-Ursprüngliche Nachricht-
Von: Florian Haas
Gesendet: 29.04.2010 09:06:44
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Need an idea for dynamic configuration dependng on
resource distribution
Hi Florian,
>Are you talking about innodb_buffer_pool_size?
>
On Thu, Apr 29, 2010 at 12:15 AM, Andreas Mock wrote:
> -Ursprüngliche Nachricht-
> Von: Andrew Beekhof
> Gesendet: 27.04.2010 20:56:48
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] Need an idea for dynamic configuration dependng on
> res
On 04/29/2010 12:15 AM, Andreas Mock wrote:
> -Ursprüngliche Nachricht-
> Von: Andrew Beekhof
> Gesendet: 27.04.2010 20:56:48
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] Need an idea for dynamic configuration dependng on
> res
-Ursprüngliche Nachricht-
Von: Andrew Beekhof
Gesendet: 27.04.2010 20:56:48
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Need an idea for dynamic configuration dependng on
resource distribution
>> configuration in the default case (everything o.k.). I
On Tue, Apr 27, 2010 at 2:45 PM, Andreas Mock wrote:
> Hi all,
>
> I need an idea how I could achieve the following with corosync/pacemaker.
> 2 servers in a cluster. Each server is running a resource on its own by
> pacemaker
> configuration in the default case (everything o.k.). In this scenari
-Ursprüngliche Nachricht-
Von: Michael Schwartzkopff
Gesendet: 27.04.2010 14:51:58
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Need an idea for dynamic configuration dependng on
resource distribution
>Am Dienstag, 27. April 2010 14:45:21 schrieb Andreas M
Am Dienstag, 27. April 2010 14:45:21 schrieb Andreas Mock:
> Hi all,
>
> I need an idea how I could achieve the following with corosync/pacemaker.
> 2 servers in a cluster. Each server is running a resource on its own by
> pacemaker configuration in the default case (everything o.k.). In this
> sce
Hi all,
I need an idea how I could achieve the following with corosync/pacemaker.
2 servers in a cluster. Each server is running a resource on its own by
pacemaker
configuration in the default case (everything o.k.). In this scenario the
resources
shall take as much "server estate" as possible.