[ClusterLabs] Antw: Two node Active/Active Asterisk+GFS2+DLM+fence_xvm Cluster
>>> TEG AMJG schrieb am 14.07.2016 um 23:47 in Nachricht : > Dear list > > I am quite new to PaceMaker and i am configuring a two node active/active > cluster which consist basically on something like this: > > I am using pcsd Pacemaker/Corosync: > > Clone Set: dlm-clone [dlm] > Started: [ pbx1vs3 pbx2vs3 ] > Clone Set: asteriskfs-clone [asteriskfs] > Started: [ pbx1vs3 pbx2vs3 ] > Clone Set: asterisk-clone [asterisk] > Started: [ pbx1vs3 pbx2vs3 ] > fence_pbx2_xvm(stonith:fence_xvm):Started pbx1vs3 > fence_pbx1_xvm(stonith:fence_xvm):Started pbx2vs3 > Clone Set: clvmd-clone [clvmd] > Started: [ pbx1vs3 pbx2vs3] > > Now my problem is that, for example, when i fence one of the nodes, the > other one restarts every clone resource and start them back again, same > thing happens when i stop pacemaker and corosync in one node only (pcs > cluster stop). That would mean that if i have a problem in one of my > Asterisk (for example in DLM resource or CLVMD) that would require fencing > right away, for example node pbx2vs3, the other node (pbx1vs3) will restart > every service which will drop all my calls in a well functioning node. > > All this leads to a basic question, is this a strict way for clone > resources to behave?, is it possible to configure them so they would Usually you'll find in syslog or cluster's log files more details why a resource is restarted. Without knowing these details anybody can just guess. It could be that you made a configuration error... > behave, dare i say, in a more unique way (i know about the option > globally-unique but as far as i understand that doesnt do the work). I have > been reading about clone resources for a while but there are no many > examples about what it cant do. > > Thanks in advance > > Alejandro ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Antw: Two node Active/Active Asterisk+GFS2+DLM+fence_xvm Cluster
maybe you need interleave=true in your clones 2016-07-15 8:32 GMT+02:00 Ulrich Windl : TEG AMJG schrieb am 14.07.2016 um 23:47 in Nachricht > : >> Dear list >> >> I am quite new to PaceMaker and i am configuring a two node active/active >> cluster which consist basically on something like this: >> >> I am using pcsd Pacemaker/Corosync: >> >> Clone Set: dlm-clone [dlm] >> Started: [ pbx1vs3 pbx2vs3 ] >> Clone Set: asteriskfs-clone [asteriskfs] >> Started: [ pbx1vs3 pbx2vs3 ] >> Clone Set: asterisk-clone [asterisk] >> Started: [ pbx1vs3 pbx2vs3 ] >> fence_pbx2_xvm(stonith:fence_xvm):Started pbx1vs3 >> fence_pbx1_xvm(stonith:fence_xvm):Started pbx2vs3 >> Clone Set: clvmd-clone [clvmd] >> Started: [ pbx1vs3 pbx2vs3] >> >> Now my problem is that, for example, when i fence one of the nodes, the >> other one restarts every clone resource and start them back again, same >> thing happens when i stop pacemaker and corosync in one node only (pcs >> cluster stop). That would mean that if i have a problem in one of my >> Asterisk (for example in DLM resource or CLVMD) that would require fencing >> right away, for example node pbx2vs3, the other node (pbx1vs3) will restart >> every service which will drop all my calls in a well functioning node. >> >> All this leads to a basic question, is this a strict way for clone >> resources to behave?, is it possible to configure them so they would > > Usually you'll find in syslog or cluster's log files more details why a > resource is restarted. Without knowing these details anybody can just guess. > It could be that you made a configuration error... > >> behave, dare i say, in a more unique way (i know about the option >> globally-unique but as far as i understand that doesnt do the work). I have >> been reading about clone resources for a while but there are no many >> examples about what it cant do. >> >> Thanks in advance >> >> Alejandro > > > > > > ___ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- .~. /V\ // \\ /( )\ ^`~'^ ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
