Re: [ClusterLabs] why resources are restarted when a node rejoins a cluster?

2017-07-25 Thread Kristián Feldsam 
It looks like stickiness not configured.

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html/Clusters_from_Scratch/ch05s03s02.html

S pozdravem Kristián Feldsam
Tel.: +420 773 303 353, +421 944 137 535
E-mail.: supp...@feldhost.cz

www.feldhost.cz - FeldHost™ – profesionální hostingové a serverové služby za 
adekvátní ceny.

FELDSAM s.r.o.
V rohu 434/3
Praha 4 – Libuš, PSČ 142 00
IČ: 290 60 958, DIČ: CZ290 60 958
C 200350 vedená u Městského soudu v Praze

Banka: Fio banka a.s.
Číslo účtu: 2400330446/2010
BIC: FIOBCZPPXX
IBAN: CZ82 2010  0024 0033 0446

> On 25 Jul 2017, at 16:06, Ken Gaillot  wrote:
> 
> On Mon, 2017-07-24 at 23:07 -0400, Digimer wrote:
>> On 2017-07-24 11:04 PM, ztj wrote:
>>> Hi all,
>>> I have 2 Centos nodes with heartbeat and pacemaker-1.1.13 installed,
>>> and almost everything is working fine, I have only apache configured
>>> for testing, when a node goes down the failover is done correctly,
>>> but there's a problem when a node failbacks.
>>> 
>>> For example, let's say that Node1 has the lead on apache resource,
>>> then I reboot Node1, so Pacemaker detect it goes down, then apache
>>> is promoted to the Node2 and it keeps there running fine, that's
>>> fine, but when Node1 recovers and joins the cluster again, apache is
>>> restarted on Node2 again.
>>> 
>>> Anyone knows, why resources are restarted when a node rejoins a
>>> cluster? thanks
> 
> That's not the default behavior, so something else is going on. Show
> your configuration (with any sensitive information removed) for more
> help.
> 
>> You sent this to the moderators, not the list.
>> 
>> Please don't use heartbeat, it is extremely deprecated. Please switch
>> to corosync.
> 
> Since it's CentOS, it has to be corosync, unless heartbeat was compiled
> locally.
> 
>> 
>> To offer any other advice, you need to share your config and the logs
>> from both nodes. Please respond to the list, not
>> developers-ow...@clusterlabs.org.
>> 
>> digimer
>> -- 
>> Digimer
>> Papers and Projects: https://alteeve.com/w/
>> "I am, somehow, less interested in the weight and convolutions of Einstein’s 
>> brain than in the near certainty that people of equal talent have lived and 
>> died in cotton fields and sweatshops." - Stephen Jay Gould
>> ___
>> Users mailing list: Users@clusterlabs.org
>> http://lists.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
> 
> -- 
> Ken Gaillot 
> 
> 
> 
> 
> 
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.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

___
Users mailing list: Users@clusterlabs.org
http://lists.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] why resources are restarted when a node rejoins a cluster?

2017-07-25 Thread Ken Gaillot 
On Mon, 2017-07-24 at 23:07 -0400, Digimer wrote:
> On 2017-07-24 11:04 PM, ztj wrote:
> > Hi all,
> > I have 2 Centos nodes with heartbeat and pacemaker-1.1.13 installed,
> > and almost everything is working fine, I have only apache configured
> > for testing, when a node goes down the failover is done correctly,
> > but there's a problem when a node failbacks.
> > 
> > For example, let's say that Node1 has the lead on apache resource,
> > then I reboot Node1, so Pacemaker detect it goes down, then apache
> > is promoted to the Node2 and it keeps there running fine, that's
> > fine, but when Node1 recovers and joins the cluster again, apache is
> > restarted on Node2 again.
> > 
> > Anyone knows, why resources are restarted when a node rejoins a
> > cluster? thanks

That's not the default behavior, so something else is going on. Show
your configuration (with any sensitive information removed) for more
help.

> You sent this to the moderators, not the list.
> 
> Please don't use heartbeat, it is extremely deprecated. Please switch
> to corosync.

Since it's CentOS, it has to be corosync, unless heartbeat was compiled
locally.

> 
> To offer any other advice, you need to share your config and the logs
> from both nodes. Please respond to the list, not
> developers-ow...@clusterlabs.org.
> 
> digimer
> -- 
> Digimer
> Papers and Projects: https://alteeve.com/w/
> "I am, somehow, less interested in the weight and convolutions of Einstein’s 
> brain than in the near certainty that people of equal talent have lived and 
> died in cotton fields and sweatshops." - Stephen Jay Gould
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.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

-- 
Ken Gaillot 





___
Users mailing list: Users@clusterlabs.org
http://lists.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] why resources are restarted when a node rejoins a cluster?

2017-07-24 Thread Digimer 

  
  
On 2017-07-24 11:04 PM, ztj wrote:

  
  
  
  
Hi all,
I have 2 Centos nodes with
  heartbeat and pacemaker-1.1.13 installed, and almost
  everything is working fine, I have only apache configured
  for testing, when a node goes down the failover is done
  correctly, but there's a problem when a node failbacks.

For example, let's say that
  Node1 has the lead on apache resource, then I reboot
  Node1, so Pacemaker detect it goes down, then apache is
  promoted to the Node2 and it keeps there running fine,
  that's fine, but when Node1 recovers and joins the cluster
  again, apache is restarted on Node2 again.

Anyone knows, why resources
  are restarted when a node rejoins a cluster? thanks
  


You sent this to the moderators, not the list.

Please don't use heartbeat, it is extremely deprecated. Please
switch to corosync.

To offer any other advice, you need to share your config and the
logs from both nodes. Please respond to the list, not
developers-ow...@clusterlabs.org.

digimer
-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
  


___
Users mailing list: Users@clusterlabs.org
http://lists.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