<html><head></head><body>If your 1 node cluster hits a split brain situation, you have got bigger problems!<br>
<br>
Unless you can guarantee that a cluster can not encounter a split brain (to the same degree a 1 node cluster can!), any cluster solution worth installing should have a robust fencing method. Preferably more than one, really.<br>
<br>
Therein lies the true value: what happens when something really messes up? How much do you really want to drive to the DC at 3am?<br><br><div class="gmail_quote">On April 18, 2017 1:36:21 PM EDT, Dimitri Maziuk <dmaziuk@bmrb.wisc.edu> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 04/18/2017 02:47 AM, Ulrich Windl wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> IMHO: a valid cluster software works starting at 1 node, then per induction<br /> also for n+1 nodes.<br /></blockquote><br />I'm not sure what a valid fencing configuration would be in a one-node<br />cluster, and since -- all together now -- YOU HAVE TO HAVE FENCING!..<br />Perhaps you should consider a different definition or different cluster<br />software.<br /><br />Oh, wait...</pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>