Re: [ClusterLabs] Pacemaker resources are not scheduled

On Mon, 2018-04-16 at 23:52 +0800, lkxjtu wrote: > > Lkxjtu, > > > On 14/04/18 00:16 +0800, lkxjtu wrote: > >> My cluster version: > >> Corosync 2.4.0 > >> Pacemaker 1.1.16 > >>  > >> There are many resource anomalies. Some resources are only > monitored > >> and not recovered. Some resources are

Re: [ClusterLabs] Booth fail-over conditions

Zach Anderson writes: > Hey all, > > new user to pacemaker/booth and I'm fumbling my way through my first proof > of concept. I have a 2 site configuration setup with local pacemaker > clusters at each site (running rabbitmq) and a booth arbitrator. I've > successfully

Re: [ClusterLabs] Pacemaker resources are not scheduled

> Lkxjtu, > On 14/04/18 00:16 +0800, lkxjtu wrote: >> My cluster version: >> Corosync 2.4.0 >> Pacemaker 1.1.16 There are many resource anomalies. Some resources are only monitored >> and not recovered. Some resources are not monitored or recovered. >> Only one resource of vnm is scheduled

[ClusterLabs] attrd/attrd_updater asynchronous behavior

Hi, I have a question in regard with attrd asynchronous behavior In PAF, during the election process to pick the best PgSQL master, we are using private attributes to publish the status (LSN) of each pgsql instances during the pre-promote action. Because we need these LSN from each nodes during

Re: [ClusterLabs] attrd/attrd_updater asynchronous behavior

I got an answer on IRC from Ken Gaillot. Bellow his answer for tracking purpose. On Mon, 16 Apr 2018 23:28:39 +0200 Jehan-Guillaume de Rorthais wrote: [...] > * does looping until the value becomes available is enough to conclude all > other node have the same value? Or is

Re: [ClusterLabs] Fwd: Re: [Cluster-devel] [PATCH] dlm: prompt the user SCTP is experimental

Hi David and Mark, I compiled my own DLM kernel module with getting ride of "return -EINVAL;" line. Then did some tests with new DLM kernel module, under two-ring cluster plus "protocol=tcp" setting in /etc/dlm/dlm.conf. 1) if both networks were OK, all the tests were passed. 2) if I broken the

[ClusterLabs] 答复: No slave is promoted to be master

I check the status again. It is not not promoted but it promoted about 15 minutes after the cluster starts. I try in three labs and the results are same: The promotion happens 15 minutes after the cluster starts. Why is there about 15 minutes delay every time? Apr 16 22:08:32 node1

Re: [ClusterLabs] 答复: No slave is promoted to be master

Отправлено с iPhone > 17 апр. 2018 г., в 7:16, 范国腾 написал(а): > > I check the status again. It is not not promoted but it promoted about 15 > minutes after the cluster starts. > > I try in three labs and the results are same: The promotion happens 15 > minutes

Re: [ClusterLabs] HALVM monitor action fail on slave node. Possible bug?

Hi Emmanuel, thank you for you support. I did a lot of checks during the WE and there are some updates: - Main problem is that ocf:heartbeat:LVM is old. The current version on centos 7 is 3.9.5 (package resource-agents). More precisely, in 3.9.5 the monitor function has one important assumption:

[ClusterLabs] No slave is promoted to be master

Hi， We install a new lab which only have the postgres resource and the vip resource. After the cluster is installed, the status is ok: only node is master and the other is slave. Then I run "pcs cluster stop --all" to close the cluster and then I run the "pcs cluster start --all" to start the

Re: [ClusterLabs] Pacemaker resources are not scheduled

Lkxjtu, On 14/04/18 00:16 +0800, lkxjtu wrote: > My cluster version: > Corosync 2.4.0 > Pacemaker 1.1.16 > > There are many resource anomalies. Some resources are only monitored > and not recovered. Some resources are not monitored or recovered. > Only one resource of vnm is scheduled normally,