[ClusterLabs] Notification agent and Notification recipients

Hi, Any idea what could have gone wrong or if there are other ways to achieve the same ? Regards, Sriram. -- Forwarded message -- From: Sriram Date: Thu, Aug 3, 2017 at 12:31 PM Subject: Notification agent and Notification recipients To: Cluster Labs - All

[ClusterLabs] verify status starts at 100% and stays there?

I have drbd 9.0.8. I started an online verify, and immediately checked status, and I see... ha11a:/ha01_mysql/trimtester # drbdadm status ha01_mysql role:Primary disk:UpToDate ha11b role:Secondary replication:VerifyT peer-disk:UpToDate done:100.00 ...which looks like it is finished, but

Re: [ClusterLabs] Antw: Re: Antw: DRBD and SSD TRIM - Slow! -- RESOLVED!

For anyone else who has this problem, we have reduced the time required to trim a 1.3TB volume from 3 days to 1.5 minutes. Initially, we had used mdraid to build a raid0 array with a 32K chunk size. We initialized it as a drbd disk, synced it, built an lvm logical volume on it, and created an

[ClusterLabs] Fwd: Multi cluster

Hi, I am new to clustering so please ignore if my Question sounds silly, i have a requirement were in i need to create cluster for ERP application with apache, VIP component,below is the scenario We have 5 Sites, 1. DC 2. Site A 3. Site B 4. Site C 5. Site D Over here we need to configure HA as

[ClusterLabs] Notification agent and Notification recipients

Hi Team, We have a four node cluster (1 active : 3 standby) in our lab for a particular service. If the active node goes down, one of the three standby node becomes active. Now there will be (1 active : 2 standby : 1 offline). Is there any way where this newly elected node sends notification