This talks about how manual fencing isn't actual fencing;
https://fedorahosted.org/cluster/wiki/Fence
There was a page where it was said that manual fencing was in no way
supported, but I can't find it at the moment.
The reason it is not safe is that an admin is likely to issue it in a
panic while trying to get a hung cluster back online. If this happens
without first ensuring the peer node(s) is fenced, you can walk into a
split-brain.
digimer
On 10/02/2012 09:43 AM, Parvez Shaikh wrote:
Hi Digimer,
Could you please give me reference/case studies of problem about why
manual fencing was dropped and how automated fencing is fixing those?
Thanks,
Parvez
On Tue, Oct 2, 2012 at 7:08 PM, Digimer <lists@xxxxxxxxxx
<mailto:lists@xxxxxxxxxx>> wrote:
On 10/02/2012 04:00 AM, Parvez Shaikh wrote:
What kind of cluster is this - an academic project or production
quality
solution?
If its former - go for manual fencing. You wont need fence
device but
failover wont be automatic
*Please* don't do this. Manual fencing support was dropped for a
reason. It's *far* too easy to mess things up when an admin uses it
before identifying a problem.
If its later - yes you'll need fence device
This is the only sane option; Academic or production. Fencing is an
integral part of the cluster and you do yourself no favour by not
learning it in an academic setup.
--
Digimer
Papers and Projects: https://alteeve.ca
"Hydrogen is just a colourless, odourless gas which, if left alone
in sufficient quantities for long periods of time, begins to think
about itself."
--
Digimer
Papers and Projects: https://alteeve.ca
"Hydrogen is just a colourless, odorless gas which, if left alone in
sufficient quantities for long periods of time, begins to think about
itself."
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
