Fixed previous mail
clean_start=1 disable the startup fencing and if you use a quorum disk in your cluster without expected_votes=1, when a node start after it has been fenced, the node dosn't try to fence di remain node and doesn't try to start the service, because rgmanager need a cluster quorate, so many people around say clean_start=1 is dangerous, but no one give a clear reason, in my production cluster a i have clvm+vg in exclusive mode+(clean_start=1)+(master_
clean_start=1 disable the startup fencing and if you use a quorum disk in your cluster without expected_votes=1, when a node start after it has been fenced, the node dosn't try to fence di remain node and doesn't try to start the service, because rgmanager need a cluster quorate, so many people around say clean_start=1 is dangerous, but no one give a clear reason, in my production cluster a i have clvm+vg in exclusive mode+(clean_start=1)+(master_
wins). so if you can explain me where is the problem :) i apriciate
2013/9/11 Digimer <lists@xxxxxxxxxx>
On 11/09/13 12:04, emmanuel segura wrote:This is a very bad idea and is asking for a split-brain, the main reason fencing exists at all.
Hello Pascal
For disable startup fencing you need clean_start=1 in the fence_daemon
tag, i saw in your previous mail you are using expected_votes="1", with
this setting every cluster node will be partitioned into two clusters
and operate independently, i recommended using a quorim disk with
master_wins parameter
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without access to education?
--
esta es mi vida e me la vivo hasta que dios quiera
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
