Re: [ClusterLabs] In N+1 cluster, add/delete of one resource result in other node resources to restart

Thanks Aswathi. (My account had stopped working due to mail bounces, never seen that occur on gmail accounts) Ken, Answers to your questions are below: *1. Using force option* A) During our testing we had observed that in some instances the resource deletion would fail and that's why we added

Re: [ClusterLabs] Syncing data and reducing CPU utilization of cib process

Thank you Lars. Yes, subscribing will be better. Will look into it. We have already started working on reducing the data that goes into CIB file. -Regards Nikhil On Mon, Apr 3, 2017 at 6:41 PM, Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > On Mon, Apr 03, 2017 at 03:44:21PM +053

Re: [ClusterLabs] Syncing data and reducing CPU utilization of cib process

bytes into 13546 (ratio 31:1ms -Regards Nikhil On Mon, Apr 3, 2017 at 11:38 AM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Ken, > > The CIB file is not being updated that often. > I took a packet capture and don't see the node sending any message to > other nodes (o

Re: [ClusterLabs] Syncing data and reducing CPU utilization of cib process

com> wrote: > On 03/31/2017 06:44 AM, Nikhil Utane wrote: > > We are seeing this log in pacemaker.log continuously. > > > > Mar 31 17:13:01 [6372] 0005B932ED72cib: info: > > crm_compress_string: Compressed 436756 bytes into 14635 (ratio 29:1

Re: [ClusterLabs] Syncing data and reducing CPU utilization of cib process

, 2017 at 12:08 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Hi, > > In our current design (which we plan to improve upon) we are using the CIB > file to synchronize information across active and standby nodes. > Basically we want the standby node to take the config

[ClusterLabs] Syncing data and reducing CPU utilization of cib process

Hi, In our current design (which we plan to improve upon) we are using the CIB file to synchronize information across active and standby nodes. Basically we want the standby node to take the configuration that was used by the active node so we are adding those as resource attributes. This ensures

Re: [ClusterLabs] Antw: Running two independent clusters

t; On 03/22/2017 11:08 PM, Nikhil Utane wrote: > > I simplified when I called it as a service. Essentially it is a complete > > system. > > It is an LTE eNB solution. It provides LTE service (service A) and now > > we need to provide redundancy for another different but relat

Re: [ClusterLabs] Antw: Running two independent clusters

05:23 AM, Nikhil Utane wrote: > > Hi Ulrich, > > > > It's not an option unfortunately. > > Our product runs on a specialized hardware and provides both the > > services (A & B) that I am referring to. Hence I cannot have service A > > running on some nodes

Re: [ClusterLabs] Antw: Re: Antw: Running two independent clusters

I need 2 clusters to be running independently of each other on same node. -Nikhil On Wed, Mar 22, 2017 at 6:36 PM, Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Nikhil Utane <nikhil.subscri...@gmail.com> schrieb am 22.03.2017 um > 11:23 in &

Re: [ClusterLabs] Antw: Running two independent clusters

@rz.uni-regensburg.de> wrote: > >>> Nikhil Utane <nikhil.subscri...@gmail.com> schrieb am 22.03.2017 um > 07:48 in > Nachricht > <CAGNWmJV05-YG+f9VNG0Deu-2xo7Lp+kRQPOn9sWYy7Jz=0g...@mail.gmail.com>: > > Hi All, > > > > First of all, let me thank ever

[ClusterLabs] Running two independent clusters

Hi All, First of all, let me thank everyone here for providing excellent support from the time I started evaluating this tool about a year ago. It has helped me to make a timely and good quality release of our Redundancy solution using Pacemaker & Corosync. (Three cheers :)) Now for our next

Re: [ClusterLabs] Get rid of reload altogether

resource attributes change. Would it be easier to modify the pacemaker source code and ignore this change of value? -Regards Nikhil On Wed, Nov 30, 2016 at 8:46 PM, Jan Pokorný <jpoko...@redhat.com> wrote: > On 28/11/16 09:44 +0530, Nikhil Utane wrote: > > I understand the whole co

Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: Unexpected Resource movement after failover

I think it was a silly mistake. "placement-strategy" was not enabled. We have enabled it now and testing it out. Thanks On Mon, Oct 24, 2016 at 7:35 PM, Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Nikhil Utane <nikhil.subscri...@gmail.com>

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

I had set resource utilization to 1. Even then it scheduled 2 resources. Doesn't it honor utilization resources if it doesn't find a free node? -Nikhil On Mon, Oct 24, 2016 at 4:43 PM, Vladislav Bogdanov <bub...@hoster-ok.com> wrote: > 24.10.2016 14:04, Nikhil Utane wrote: > >

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

That is what happened here :(. When 2 nodes went down, two resources got scheduled on single node. Isn't there any way to stop this from happening. Colocation constraint is not helping. -Regards Nikhil On Sat, Oct 22, 2016 at 12:57 AM, Vladislav Bogdanov wrote: >

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 10/17/2016 09:55 AM, Nikhil Utane wrote: > > I see these prints. > > > > pengine: info: rsc_merge_weights:cu_4: Rolling back scores from cu_3 > > pengine:debug: native_assign_node:Assigning Redun_CU

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

:-INFINITY) On Mon, Oct 17, 2016 at 8:16 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > This is driving me insane. > > This is how the resources were started. Redund_CU1_WB30 was the DC which > I rebooted. > cu_4 (ocf::redundancy:RedundancyRA): Started Redund_

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

core:-INFINITY) cu_4 with cu_5 (score:-INFINITY) cu_5 with cu_4 (score:-INFINITY) Ticket Constraints: -Thanks Nikhil On Fri, Oct 14, 2016 at 5:26 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Hi, > > Thank you for the responses so far. > I added reverse colocati

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

; violate "a not with b"? Can someone confirm that colocation is required to be configured both ways? -Thanks Nikhil On Fri, Oct 14, 2016 at 1:09 PM, Vladislav Bogdanov <bub...@hoster-ok.com> wrote: > On October 14, 2016 10:13:17 AM GMT+03:00, Ulrich Windl < > ulrich

Re: [ClusterLabs] Unexpected Resource movement after failover

for the quick answer, guys. -Nikhil On Thu, Oct 13, 2016 at 7:59 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > On Thu, Oct 13, 2016 at 4:59 PM, Nikhil Utane > <nikhil.subscri...@gmail.com> wrote: > > Hi, > > > > I have 5 nodes and 4 resources configur

Re: [ClusterLabs] Antw: Unexpected Resource movement after failover

ere), like in this table (produced with R): > > [,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] [,9] [,10] > [1,] "A" "A" "A" "A" "B" "B" "B" "C" "C" "D" > [2,] "B" &q

Re: [ClusterLabs] Unexpected Resource movement after failover

Additional info, -Nikhil On Thu, Oct 13, 2016 at 7:29 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Hi, > > I have 5 nodes and 4 resources configured. > I have configured constraint such that no two resources can be co-located. > I brought down a node (which

[ClusterLabs] Unexpected Resource movement after failover

Hi, I have 5 nodes and 4 resources configured. I have configured constraint such that no two resources can be co-located. I brought down a node (which happened to be DC). I was expecting the resource on the failed node would be migrated to the 5th waiting node (that is not running any resource).

Re: [ClusterLabs] Limiting number of nodes that can join into a cluster

Hmm. That is also a possibility. Thanks Chrissie. On Tue, Jun 28, 2016 at 6:13 PM, Christine Caulfield <ccaul...@redhat.com> wrote: > On 28/06/16 13:27, Nikhil Utane wrote: > > Hi Klaus, > > > > I am using multicast to avoid having to configure the host names. >

[ClusterLabs] Limiting number of nodes that can join into a cluster

Hi, I want to limit the number of nodes that can form a cluster to single digit (say 6). I can do it using application-level logic but would like to know if there is any option in Corosync that would do it for me. (Didn't find one). If there is some #define, can I change it without any

Re: [ClusterLabs] Recovering after split-brain

Hmm. I will then work towards bringing this in. Thanks for your input. On Wed, Jun 22, 2016 at 10:44 AM, Digimer <li...@alteeve.ca> wrote: > On 22/06/16 01:07 AM, Nikhil Utane wrote: > > I don't get it. Pacemaker + Corosync is providing me so much of > > functionality. >

Re: [ClusterLabs] Recovering after split-brain

I don't get it. Pacemaker + Corosync is providing me so much of functionality. For e.g. if we leave out the condition of split-brain for a while, then it provides: 1) Discovery and cluster formation 2) Synchronization of data 3) Heartbeat mechanism 4) Swift failover of the resource 5) Guarantee

Re: [ClusterLabs] Recovering after split-brain

Let me give the full picture about our solution. It will then make it easy to have the discussion. We are looking at providing N + 1 Redundancy to our application servers, i.e. 1 standby for upto N active (currently N<=5). Each server will have some unique configuration. The standby will store

[ClusterLabs] Recovering after split-brain

Hi, For our solution we are making a conscious choice to not use quorum/fencing as for us service availability is more important than having 2 nodes take up the same active role. Split-brain is not an issue for us (at least i think that way) since we have a second line of defense. We have clients

Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

This solved the problem. Thanks. :) On Mon, Jun 6, 2016 at 9:49 AM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Yes, everything is (almost) latest version. Will give this a try. Thanks > Jan. > > On Fri, Jun 3, 2016 at 9:04 PM, Jan Pokorný <jpoko...@redhat.com>

[ClusterLabs] Minimum configuration for dynamically adding a node to a cluster

Hi, Would like to know the best and easiest way to add a new node to an already running cluster. Our limitation: 1) pcsd cannot be used since (as per my understanding) it communicates over ssh which is prevented. 2) No manual editing of corosync.conf So what I am thinking is, the first node

[ClusterLabs] Few questions regarding corosync authkey

Hi, Would like to understand how secure is the corosync authkey. As the authkey is a binary file, how is the private key saved inside the authkey? What safeguard mechanisms are in place if the private key is compromised? For e.g I don't think it uses any temporary session key which refreshes

Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

still doesn't show the cluster name. [root@airv_cu root]# pcs status Cluster name: -Regards Nikhil On Fri, Jun 3, 2016 at 4:46 PM, Klaus Wenninger <kwenn...@redhat.com> wrote: > On 06/03/2016 01:03 PM, Nikhil Utane wrot

[ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

Hi, The node is up alright. [root@airv_cu pcs]# pcs cluster status Cluster Status: Stack: corosync Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition WITHOUT quorum Last updated: Fri Jun 3 11:01:32 2016 Last change: Fri Jun 3 09:57:52 2016 by hacluster via crmd on airv_cu 2

Re: [ClusterLabs] Antw: Re: Using different folder for /var/lib/pacemaker and usage of /dev/shm files

Yes, we do have our application using shared memory which is what we see when the cluster is down. On Tue, May 17, 2016 at 10:53 PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 05/17/2016 12:02 PM, Nikhil Utane wrote: > > OK. Will do that. > > > > Actually I g

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

Hi Honza, Just checking if you have the official patch available for this issue. As far as I am concerned barring couple of issues, everything seems to be working fine on our big-endian system. Much relieved. :) -Thanks Nikhil On Thu, May 5, 2016 at 3:24 PM, Nikhil Utane <nikhil.subs

Re: [ClusterLabs] Antw: Re: Using different folder for /var/lib/pacemaker and usage of /dev/shm files

what size is needed. Thank you Ken and Ulrich. On Tue, May 17, 2016 at 8:23 PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 05/17/2016 04:07 AM, Nikhil Utane wrote: > > What I would like to understand is how much total shared memory > > (approximately) would Pacemaker need

Re: [ClusterLabs] Antw: Re: Using different folder for /var/lib/pacemaker and usage of /dev/shm files

. > > Maybe there should be a tool that identifies and cleans up obsolete shared > memory. > I don't understand the part talking about the size of /dev/shm: It's > shared memory. See "kernel.shmmax" and "kernel.shmall" in you sysctl > settings (/etc/sysctl.conf).

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

Last change: Fri May 6 12:08:23 2016 1 node and 0 resources configured Let me check whether qt-blackbox gives any details. -Thanks Nikhil On Fri, May 6, 2016 at 5:46 PM, Jan Pokorný <jpoko...@redhat.com> wrote: > On 06/05/16 16:59 +0530, Nikhil Utane wrote: > > > >

[ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

Hi, Continuing with my adventure to run Pacemaker & Corosync on our big-endian system, I managed to get past the corosync issue for now. But facing an issue in running Pacemaker. Seeing following messages in corosync.log. pacemakerd: warning: pcmk_child_exit: The cib process (2) can no

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

ion seems to >> be going through fine. Will check other things. >> > > Your patch is incorrect and actually doesn't work. As I said (when > pointing you to schedwrk.c), I will send you proper patch, but fix that > issue correctly is not easy. > > Regards, >

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

static const void * 59 handle2void (hdb_handle_t h) { union u u={}; u.h = h; return u.v; } After initializing (as highlighted), the corosync initialization seems to be going through fine. Will check other things. -Regards Nikhil On Tue, May 3, 2016 at 7:04 PM, Nikhil Utane <nikhil.subs

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

vant > bugs in corosync got fixed at that time. Don't know what is the > situation with the latest version. > > Thanks, > > Dejan > > > Regards, > > Honza > > > > > > > >Regards, > > >Klaus > > > > > >On 05/02/2016 06:44

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

at 1:00 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > So what I understand what you are saying is, if the HW is bi-endian, then > enable LE on PPC. Is that right? > Need to check on that. > > On Mon, May 2, 2016 at 12:49 PM, Nikhil Utane <nikhil.subscri...@gmail.c

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

So what I understand what you are saying is, if the HW is bi-endian, then enable LE on PPC. Is that right? Need to check on that. On Mon, May 2, 2016 at 12:49 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Sorry about my ignorance but could you pls elaborate what do you mean

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

th Klaus. Give a try to ppcle. Also make sure all nodes > are little-endian. Corosync should work in mixed BE/LE environment but > because it's not tested, it may not work (and it's a bug, so if ppcle works > I will try to fix BE). > > Regards, > Honza > > > >> Rega

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

Re-sending as I don't see my post on the thread. On Sun, May 1, 2016 at 4:21 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Hi, > > Looking for some guidance here as we are completely blocked otherwise :(. > > -Regards > Nikhil > > On Fri, Apr 29, 2

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

Hi, Looking for some guidance here as we are completely blocked otherwise :(. -Regards Nikhil On Fri, Apr 29, 2016 at 6:11 PM, Sriram wrote: > Corrected the subject. > > We went ahead and captured corosync debug logs for our ppc board. > After log analysis and comparison

Re: [ClusterLabs] Help required for N+1 redundancy setup

Thanks Ken for the detailed response. I suppose I could even use some of the pcs/crm CLI commands then. Cheers. On Wed, Mar 16, 2016 at 8:27 PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 03/16/2016 05:22 AM, Nikhil Utane wrote: > > I see following info gets updated in

Re: [ClusterLabs] Security with Corosync

yum install. On Wed, Mar 16, 2016 at 10:29 PM, Jan Friesse <jfrie...@redhat.com> wrote: > Nikhil Utane napsal(a): > >> Honza, >> >> In my CIB I see the infrastructure being set to cman. pcs status is >> reporting the same. >> >> > name="cl

Re: [ClusterLabs] Help required for N+1 redundancy setup

I see following info gets updated in CIB. Can I use this or there is better way? On Wed, Mar 16, 2016 at 12:40 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Hi Ken, > > Sorry about the long delay. This activity was de-focussed but now it's > back on track. > &

Re: [ClusterLabs] Help required for N+1 redundancy setup

and figured out? Thanks. Nikhil On Sat, Jan 9, 2016 at 3:31 AM, Ken Gaillot <kgail...@redhat.com> wrote: > On 01/08/2016 11:13 AM, Nikhil Utane wrote: > >> I think stickiness will do what you want here. Set a stickiness higher > >> than the original node's preference, and the

Re: [ClusterLabs] Security with Corosync

. And I did a failover and the third node took over without any issue. How is the 3rd node participating in the cluster if it doesn't have the authkey? On Fri, Mar 11, 2016 at 4:15 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Perfect. Thanks for the quick response Honza. > >

Re: [ClusterLabs] Security with Corosync

Perfect. Thanks for the quick response Honza. Cheers Nikhil On Fri, Mar 11, 2016 at 4:10 PM, Jan Friesse <jfrie...@redhat.com> wrote: > Nikhil, > > Nikhil Utane napsal(a): > >> Hi, >> >> I changed some configuration and captured packets. I can see

Re: [ClusterLabs] Security with Corosync

AM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Hi, > > Does corosync provide mechanism to secure the communication path between > nodes of a cluster? > I would like all the data that gets exchanged between all nodes to be > encrypted. > > A quick goog

[ClusterLabs] Security with Corosync

Hi, Does corosync provide mechanism to secure the communication path between nodes of a cluster? I would like all the data that gets exchanged between all nodes to be encrypted. A quick google threw up this link: https://github.com/corosync/corosync/blob/master/SECURITY Can I make use of it

Re: [ClusterLabs] Help required for N+1 redundancy setup

nside my OCF agent? Use crm command to query? Thank You. On Tue, Dec 22, 2015 at 9:44 PM, Nikhil Utane <nikhil.subscri...@gmail.com> wrote: > Thanks to you Ken for giving all the pointers. > Yes, I can use service start/stop which should be a lot simpler. Thanks > again. :) > >

Re: [ClusterLabs] Passing and binding to virtual IP in my service

that. On Fri, Jan 8, 2016 at 1:41 PM, Solutions Solutions <solution...@gmail.com> wrote: > hi Nikhil, > can you send me the N+1 redundancy configuration file,which you posted > earlier. > > On Thu, Jan 7, 2016 at 2:58 PM, Nikhil Utane <nikhil.subscri...@gmail.com> > w

[ClusterLabs] Passing and binding to virtual IP in my service

Hi, I have my cluster up and running just fine. I have a dummy service that sends UDP packets out to another host. Resource Group: MyGroup ClusterIP (ocf::heartbeat:IPaddr2): Started node1 UDPSend(ocf::nikhil:UDPSend): Started node1 If I ping to the virtual IP from

Re: [ClusterLabs] Passing and binding to virtual IP in my service

gt; On 01/07/2016 05:28 AM, Nikhil Utane wrote: > > So my question is, how to pass the virtual IP to my UDPSend OCF agent so > > that it can then bind to the vip? This will ensure that all messages > > initiated by my UDPSend goes from vip. > > Hi, > > I don't know how pi

Re: [ClusterLabs] Help required for N+1 redundancy setup

Thanks to you Ken for giving all the pointers. Yes, I can use service start/stop which should be a lot simpler. Thanks again. :) On Tue, Dec 22, 2015 at 9:29 PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 12/22/2015 12:17 AM, Nikhil Utane wrote: > > I have prepared a write-u

Re: [ClusterLabs] Help required for N+1 redundancy setup

=sharing Let me know if you face any issue in accessing the above link. Thanks. On Thu, Dec 3, 2015 at 11:34 PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 12/03/2015 05:23 AM, Nikhil Utane wrote: > > Ken, > > > > One more question, if i have to propagate co

[ClusterLabs] Help required for N+1 redundancy setup

Hi, I am evaluating whether it is feasible to use Pacemaker + Corosync to add support for clustering/redundancy into our product. Our objectives: 1) Support N+1 redundancy. i,e. N Active and (up to) 1 Standby. 2) Each node has some different configuration parameters. 3) Whenever any active node