[Pacemaker] Corosync node detection working too good

Hello all, still working on my nodes and although the last problem is not officially solved (I hard coded certain versions of the packages and that seems to be ok now) I have a different interesting feature I need to handle. I am setting up my nodes by default as single node setups. But today

Re: [Pacemaker] Corosync node detection working too good

On 10/04/2010 02:04 AM, Stephan-Frank Henry wrote: Hello all, still working on my nodes and although the last problem is not officially solved (I hard coded certain versions of the packages and that seems to be ok now) I have a different interesting feature I need to handle. I am setting up

Re: [Pacemaker] Fail over algorithm used by Pacemaker

On 10/03/2010 07:01 AM, hudan studiawan wrote: Hi, I want to start to contribute to Pacemaker project. I start to read Documentation and try some basic configurations. I have a question: what kind of algorithm used by Pacemaker to choose another node when a node die in a cluster? Is there any

Re: [Pacemaker] Dependency on either of two resources

Hi, a similar or related use case that we tried to solve without success: - a stretch cluster with two disk boxes - a LUN on each disk box guarded by an individual SFEX - a mirror (raid1 or clvm) that survives an outage of one disk box - the mirror should be started if at least one SFEX can be

[Pacemaker] rename all nodes of a cluster

Hi Clusterlabs mailing list, I have a running cluster with three nodes. For some reason I had to change all host names and their IP address for the interface eth0 The communication channel is not affected, bindnetaddr mcastaddr mcastport will be the same. is there an easy way to rename the

Re: [Pacemaker] resource stop timeout broken in 1.0 branch tip

2010/10/2 Andreas Hofmeister a...@collax.com: Hi, it seems to me that patch  http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/8241f689bf9f broke  timeouts for stop operations. The observable effect is that the timeout for stop operations is always 125s, regardless what was specified in

[Pacemaker] crm_mon SNMP function

Hi all, I use openais/pacemaker v.1.1.2 on SLES 11.1 and would like to use the SNMP function of crm_mon. But this part is documented really scanty (e.g. the part for configuring SNMP notifications is blank). I found out that there is a special MIB named linux-ha-mib but I don´t know how to

Re: [Pacemaker] [Problem or Enhancement]When attrd reboots, a fail count is initialized.

Hi Andrew, Thank you for comment. Is the change of this attrd and crmd difficult? I dont think so. But its not a huge priority because I've never heard of attrd actually crashing. So while I agree that its theoretically a problem, in practice no-one is going to hit this in

[Pacemaker] Recommend Fencing device

Hi Which fencing devices will you recommend? I want to use a device which will give as less problems as possible on configuring a fencing resource for 3 node cluster. Regards, Pavlos ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org

[Pacemaker] Patch for slow remote connections

Hi This patch solves slow responses from remote nodes. Author is Al Stone (in CC); he's not on the list as far as I know. I've tested the patch and it does do the trick. Without the patch response was ~3 seconds, while now it's ~0.3 seconds. Index: pacemaker-1.1.2+hg20100918/cib/remote.c

[Pacemaker] Election Timeout and node became the Pending state.

Hi, We tested complicated node trouble. An error of Election Timeout occurred then. * Pacemaker:pacemaker-1.0.9.1 * heartbeat-3.0.3-2.3.el5 * cluster-glue:cluster-glue-1.0.6-1.6.el5 * resource-agents-1.0.3-1.0.dev.b7a3b1973ba7 We tested it in the next procedure. Step1) Start all nodes.