[Pacemaker] MySQL startup slow on OCFS2

Florian Haas florian.haas at linbit.com
Thu May 27 10:21:12 EDT 2010



On 2010-05-27 16:12, daniel qian wrote:
> 
> On 2010-05-27, at 5:06 AM, Florian Haas wrote:
> 
>> On 2010-05-26 16:26, daniel qian wrote:
>>> I followed this link to setup a two-node cluster on Ubuntu 10.4 - https://wiki.ubuntu.com/ClusterStack/LucidTesting#Pacemaker,%20drbd8%20and%20OCFS2%20or%20GFS2
>>>
>>> Everything is working fine except for running MySQL on both nodes with MySQL datadir set to the drbd based OCFS2 disk space.  Everytime I run command 'service mysql start'  on the second node to start up MySQL it takes a much longer time than it does on the first one to start. I tried changing the order of the two nodes to start MySQL it is always the node that starts the second MySQL. 
>>
>> Don't do that.
>> Don't do that.
>> Don't do that.
>>
> 
> I assume you mean that for only MySQL part. Any explanation?

MySQL was not built for multiple MySQL daemons (whether they are on
physically separate hosts or not) to handle a single set of MySQL data
files. And it's completely irrelevant what storage those data files are on.

There is an extremely cruel workaround to force MySQL to do this if you
only ever use MyISAM tables, but I won't even get into that. There are
also a few 3rd party storage engines not typically bundled with MySQL
distro packages that allow this under some circumstances. But InnoDB, at
this point, won't. Don't try to pretend that it does.

Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100527/75542615/attachment-0003.sig>


More information about the Pacemaker mailing list