Percona Server with XtraDB

--innodb_doublewrite_path should accept absolute location

Reported by Vadim Tkachenko on 2010-05-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
High
Unassigned

Bug Description

Currently --innodb_doublewrite_path can be set only relatively to --innodb_data_home_dir, but it restricts usability.
I want to be able to set it to any location.

Changed in percona-server:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → 5.1.46-rel11

OK
It will be change to "innodb_doublewrite_fullpath", and made independent from innodb_data_home_dir.

Yasufumi,

Why change the name ?

There is for example innodb_log_file_path which I can also specify
relatively to homedir or
as /path/to/logdir

On Mon, May 24, 2010 at 6:49 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> OK
> It will be change to "innodb_doublewrite_fullpath", and made independent
> from innodb_data_home_dir.
>
> --
> --innodb_doublewrite_path should accept absolute location
> https://bugs.launchpad.net/bugs/584299
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
>
> Status in Percona Server with XtraDB: Triaged
>
> Bug description:
> Currently --innodb_doublewrite_path can be set only relatively to
> --innodb_data_home_dir, but it restricts usability.
> I want to be able to set it to any location.
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/

Peter,

Ignoring innodb_data_home_dir is different behavior from original parameter "innodb_data_file_path".
(Even it can be set relative from "datadir", doublewrite buffer is datafile)

How to make explicit by its name...
Do you have any idea about naming to explicit ignoring "innodb_data_file_path"?

Peter Zaitsev (pz-percona) wrote :

I do not understand you. Why you can't specify double write buffer location
same as you specify location for logs ?
What it has to do with ignoring innodb_data_file_path ?

On Mon, May 24, 2010 at 9:15 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> Peter,
>
> Ignoring innodb_data_home_dir is different behavior from original parameter
> "innodb_data_file_path".
> (Even it can be set relative from "datadir", doublewrite buffer is
> datafile)
>
> How to make explicit by its name...
> Do you have any idea about naming to explicit ignoring
> "innodb_data_file_path"?
>
> --
> --innodb_doublewrite_path should accept absolute location
> https://bugs.launchpad.net/bugs/584299
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
>
> Status in Percona Server with XtraDB: Triaged
>
> Bug description:
> Currently --innodb_doublewrite_path can be set only relatively to
> --innodb_data_home_dir, but it restricts usability.
> I want to be able to set it to any location.
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/

Currently, the separate doublewrite is made by cloning datafile tablespace.
So, it is similar about usage for now.

for now,
innodb_doublewrite_path should include it's file name and have same constraints.

Do you mean "same as you specify location for logs" is...
innodb_doublewrite_path is only specifying its path and filename is fixed ("ib_doublewrite" at the path).
?

Is it OK for you and more natural than the similar usage to innodb_data_file_path?

Peter Zaitsev (pz-percona) wrote :

Yasufumi,

Similary I mean what it it accepts the full path, not just file name.

On Mon, May 24, 2010 at 10:32 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> Currently, the separate doublewrite is made by cloning datafile tablespace.
> So, it is similar about usage for now.
>
> for now,
> innodb_doublewrite_path should include it's file name and have same
> constraints.
>
> Do you mean "same as you specify location for logs" is...
> innodb_doublewrite_path is only specifying its path and filename is fixed
> ("ib_doublewrite" at the path).
> ?
>
> Is it OK for you and more natural than the similar usage to
> innodb_data_file_path?
>
> --
> --innodb_doublewrite_path should accept absolute location
> https://bugs.launchpad.net/bugs/584299
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
>
> Status in Percona Server with XtraDB: Triaged
>
> Bug description:
> Currently --innodb_doublewrite_path can be set only relatively to
> --innodb_data_home_dir, but it restricts usability.
> I want to be able to set it to any location.
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/

OK.

I will change to "innodb_doublewrite_home_dir". (filename is always ib_doublewrite)
(like innodb_log_group_home_dir)

Then it is natural usage as impression from the name, isn't it?

Changed in percona-server:
milestone: 5.1.46-rel11 → 11.0
Peter Zaitsev (pz-percona) wrote :

Yasufumi,

We specify one file right ? In this case call it innodb_doublewrite_file

On Mon, May 24, 2010 at 11:32 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> OK.
>
> I will change to "innodb_doublewrite_home_dir". (filename is always
> ib_doublewrite)
> (like innodb_log_group_home_dir)
>
> Then it is natural usage as impression from the name, isn't it?
>
> --
> --innodb_doublewrite_path should accept absolute location
> https://bugs.launchpad.net/bugs/584299
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
>
> Status in Percona Server with XtraDB: Triaged
>
> Bug description:
> Currently --innodb_doublewrite_path can be set only relatively to
> --innodb_data_home_dir, but it restricts usability.
> I want to be able to set it to any location.
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/

OK I agree, including filename.

> Yasufumi,
>
> We specify one file right ? In this case call it innodb_doublewrite_file

Changed in percona-server:
milestone: 11.0-old → 11.0
Changed in percona-server:
status: Triaged → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers