Re: write_buffer variable in my*.cnf templates is obsolete

patch to bug report
LPexportBug696007_my-innodb-heavy-4G.cnf.sh.diff

Re: write_buffer variable in my*.cnf templates is obsolete

my-huge.cnf.sh.diff
LPexportBug696007_my-huge.cnf.sh.diff

Re: write_buffer variable in my*.cnf templates is obsolete

my-large.cnf.sh.diff
LPexportBug696007_my-large.cnf.sh.diff

Re: write_buffer variable in my*.cnf templates is obsolete

my-medium.cnf.sh.diff
LPexportBug696007_my-medium.cnf.sh.diff

Re: write_buffer variable in my*.cnf templates is obsolete
affects 5.1.53 and 5.2.4 (and possibly 5.3 as well)

Re: write_buffer variable in my*.cnf templates is obsolete
write_buffer (short for write_buffer_size) is an option for myisamchk, not mysqld.

In my-medium.cnf, I have:

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

Which means that this doesn't affect the mysqld program, which you originally tried, but only the myisamchk program.

Could you please send us a copy of the my.cnf you used so that we can verify this?

Re: [Bug 696007] Re: write_buffer variable in my*.cnf templates is obsolete
The my-*.cnf files should be removed completely, they're old and quite
wrong in many ways.
Their continued existence just keeps causing trouble.

The Debian/Ubuntu packages already contain a good start for a baseline
config, this could be put in the Maria repo.

On 01/01/2011, at 12:09 AM, shinguz wrote:
> ** Patch added: "my-huge.cnf.sh.diff"
> https://bugs.launchpad.net/maria/+bug/696007/+attachment/1780304/+files/my-huge.cnf.sh.diff
>
> write_buffer variable in my*.cnf templates is obsolete
>
> Bug description:
> It looks like the write_buffer variable is not used any more:
>
> 101231 14:53:40 [ERROR] /home/mysql/product/mariadb-5.1.53/libexec/
> mysqld: unknown variable 'write_buffer=2m'
> 101231 14:53:40 [ERROR] Aborting
>
> And thus it should IMHO also be removed from the my*.cnf template
> files.

–
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Remote expertise & maintenance for MySQL/MariaDB server environments.

Follow us at http://openquery.com/blog/ & http://twitter.com/openquery

Re: [Bug 696007] Re: write_buffer variable in my*.cnf templates is obsolete
Hi Monty,

> write_buffer (short for write_buffer_size) is an option for myisamchk,
> not mysqld.
>
> Which means that this doesn't affect the mysqld program, which you
> originally tried, but only the myisamchk program.
>
> Could you please send us a copy of the my.cnf you used so that we can
> verify this?

Ups! You are absolutely right. It's my fault. Sorry about that!

Regards,
Oli

Re: [Bug 696007] Re: write_buffer variable in my*.cnf templates is obsolete
Hi Arjen,

> The my-*.cnf files should be removed completely, they're old and quite
> wrong in many ways.
> Their continued existence just keeps causing trouble.
>
> The Debian/Ubuntu packages already contain a good start for a baseline
> config, this could be put in the Maria repo.

I partly agree with you. They are not contemporary any more. But I would
not remove but refresh them.

Many MySQL/MariaDB user take them as a starting point and when we remove
them they get even worse set-ups than with the existing templates.

What settings are "quite wrong"? So we should fix these...

IMHO ideally we should have a small, medium and large (possibly with a
recommendation what small, medium and large means) config for each
storage engine.
So we end up with 3 x 4 = 12 different config files OR we have a small,
medium and large config file and have a section per storage engine in it.

Regards,
Oli

Re: [Bug 696007] Re: write_buffer variable in my*.cnf templates is obsolete
Hi Oli

On 04/01/2011, at 5:22 PM, shinguz wrote:
>> The my-*.cnf files should be removed completely, they're old and
>> quite
>> wrong in many ways.
>> Their continued existence just keeps causing trouble.
>>
>> The Debian/Ubuntu packages already contain a good start for a
>> baseline
>> config, this could be put in the Maria repo.
>
> I partly agree with you. They are not contemporary any more. But I
> would
> not remove but refresh them.
>
> Many MySQL/MariaDB user take them as a starting point and when we
> remove
> them they get even worse set-ups than with the existing templates.
>
> What settings are "quite wrong"? So we should fix these...
>
> IMHO ideally we should have a small, medium and large (possibly with a
> recommendation what small, medium and large means) config for each
> storage engine.
> So we end up with 3 x 4 = 12 different config files OR we have a
> small,
> medium and large config file and have a section per storage engine
> in it.

Please see the answer I gave before, and my solution. I did the
homework.

–
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Remote expertise & maintenance for MySQL/MariaDB server environments.

Follow us at http://openquery.com/blog/ & http://twitter.com/openquery

Launchpad bug id: 696007