Andrew,
Thanks for the feedback to my earlier questions from March 6th. I've done some
further investigation wrt the timing of what I'd call the "simple" failover
case: where an SSID that is master on the DC node is killed, and it takes
10-12 seconds before the slave SSID on the other node t
On Fri, 8 Mar 2013 19:48:11 +0100
Lars Marowsky-Bree wrote:
> > What are your experience? Is it possible to combine Resource Groups
> > and colocations? Or do I have to give up Resource Groups when using
> > colocations? If so I maybe have to restructure my resource setup to
> > colocations only.
Am Freitag, 8. März 2013, 16:37:26 schrieb Cristiane França:
> Hi,
> I have a problem when one of the server cluster starts.
> How do I remove a preferential location of a service?
> I want to remove these two configurations shown below:
>
>
> ...
>
>
>operation="eq" v
Hi,
I have a problem when one of the server cluster starts.
How do I remove a preferential location of a service?
I want to remove these two configurations shown below:
...
...
Regards,
Cristiane
Hi Emmanuel,
Thank you!
Cristiane.
On Fri, Mar 8, 2013 at 2:55 PM, emmanuel segura wrote:
> You need a order constrain
>
> order fs_after_ms inf: drbd_sistema:promote sistema_fs:start
> order pgsql_afterLfs inf: sistema_fs postgresql
>
> Or maybe you can put fs and pgsql in a group, like that
On 2013-03-08T17:43:54, Vladimir wrote:
> I already had to work around utilization by defining utilization for
> the first resource in the Resource Group. Defining utilization for
> Resource Groups didn't work for me. Furthermore I can remember that
> there were also problems by colocating Resour
You need a order constrain
order fs_after_ms inf: drbd_sistema:promote sistema_fs:start
order pgsql_afterLfs inf: sistema_fs postgresql
Or maybe you can put fs and pgsql in a group, like that you can use a
contrais like this
order foo inf: drbd_sistema:promote myservicegroup:start
2013/3/8 Cr
Hi,
My cluster is presenting error on startup of the service postgresql because
this service is being initialized before mounting the partition /sistema.
How can I configure Pacemaker to start the Postgresql only after mounting
the partition /sistema?
My server configuration:
primitive drbd_sis
On Fri, 8 Mar 2013 12:08:05 +0100
Lars Marowsky-Bree wrote:
> On 2013-03-08T11:59:33, Vladimir wrote:
>
> > Collocations were exactly what I try to avoid. The setup is planned
> > to get >15 resources (and an upper limit is not defined). I think
> > it would get pretty hard to consider all poss
Hi Hideo-san,
On Thu, Mar 07, 2013 at 10:18:09AM +0900, renayama19661...@ybb.ne.jp wrote:
> Hi Dejan,
>
> The problem was settled with your patch.
>
> However, I have a question.
> I want to use "resource_set" which Mr. Andrew proposed, but do not understand
> a method to use with crm shell.
>
On 2013-03-08T11:59:33, Vladimir wrote:
> Collocations were exactly what I try to avoid. The setup is planned to
> get >15 resources (and an upper limit is not defined). I think it would
> get pretty hard to consider all possible collocations, especially if a
> kind of automated deployment is reg
On Fri, 8 Mar 2013 11:05:01 +0100
Lars Marowsky-Bree wrote:
> On 2013-03-07T21:34:47, Vladimir wrote:
>
> > All resources are only able to run if they are distributed in the
> > right combination. A working example could like:
>
> The algorithm is somewhat simplistic, which has the advantage o
On 2013-03-07T21:34:47, Vladimir wrote:
> All resources are only able to run if they are distributed in the right
> combination. A working example could like:
The algorithm is somewhat simplistic, which has the advantage of being
fast. It works "quite well" in scenarios where there's a number of
13 matches
Mail list logo
