[Pacemaker] Need an idea for dynamic configuration dependng on resource distribution
Florian Haas
florian.haas at linbit.com
Thu Apr 29 07:06:44 UTC 2010
On 04/29/2010 12:15 AM, Andreas Mock wrote:
> -----Ursprüngliche Nachricht-----
> Von: Andrew Beekhof <andrew at beekhof.net>
> Gesendet: 27.04.2010 20:56:48
> An: The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
> Betreff: Re: [Pacemaker] Need an idea for dynamic configuration dependng on resource distribution
>
>>> configuration in the default case (everything o.k.). In this scenario the resources
>>> shall take as much "server estate" as possible.
>>
>> "server estate" == RAM/CPU etc?
>> And you can tell the app how much to use?
>
>
> a) Yes
> b) More or less. Think about mysql with innodb. One central variable is buffer_cache
> which should be "as much as possible".
Are you talking about innodb_buffer_pool_size?
If so, and regardless of the fact that this is beside the point of what
you are asking about, but if you use a buffer pool that's "as much as
possible", you'll potentially suffer pretty dramatic failover times due
to InnoDB recovery after a node crash. If you're on shared storage or
DRBD, that is. Your data would be safe but your MySQL might take minutes
or even hours to recover on startup. The webinar we did about the new
replication features in the MySQL RA covers this in some more detail.
Just my €.02.
Florian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100429/aa8a1abb/attachment-0004.sig>
More information about the Pacemaker
mailing list