I do that.  I can run up to 4 nodes in my cluster or as few as 1.  I
use a quorum disk and make sure the EXPECTED_VOTES is set to 1.  My cluster
is for development purposes, including some privileged code, so it's
susceptible to the occasional crash now and again, and as it's at home, I
try not running more than my main node (mail server, etc) if I can avoid
it, since I'm paying for the electricity.

At 05:55 PM 3/5/2004, Jack Trachtman wrote:
>I have a two node cluster with a quorum disk.
>
>I want a configuration where either node can continue to
>run even if both the other node and quorum disk are unavailable.
>
>Is giving each node its own quorum disk the only way to do this?
>
>thanks

------
+-------------------------------+----------------------------------------+
| Dan O'Reilly                  |  "There are 10 types of people in this |
| Principal Engineer            |   world: those who understand binary   |
| Process Software              |   and those who don't."                |
| http://www.process.com        |                                        |
+-------------------------------+----------------------------------------+

Dan O'Reilly <dano@process.com> wrote in message
news:6.0.0.22.2.20040305175502.01ff46f8@raptor.psccos.com...
> I do that.  I can run up to 4 nodes in my cluster or as few as 1.  I
> use a quorum disk and make sure the EXPECTED_VOTES is set to 1.  My
cluster
> is for development purposes, including some privileged code, so it's
> susceptible to the occasional crash now and again, and as it's at home, I
> try not running more than my main node (mail server, etc) if I can avoid
> it, since I'm paying for the electricity.
>

The EXPECTED_VOTES system parameter only comes into play
when the cluster is first booting.  Once the cluster is up, total votes
and quorum are recalculated any time a node comes or goes.

Your example would work if nodes only left "nicely",
including "REMOVE_NODE" in the shutdown.

DanO