Three redundancy zones

[Michael Stolz <ms...@pivotal.io>]

Is it possible to set up 3 separate redundancy zones so that a network
segmentation would have less chance of making the wrong decision about
quorum?

--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771

Re: Three redundancy zones

[Michael Stolz <ms...@pivotal.io>]

Dan,

That's exactly what I'm thinking. 3 copies of data across 3 racks, largely
eliminating the likelihood that one rack failing can cause the other to
shoot himself in the head.

--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Feb 10, 2016 12:15 PM, "Dan Smith" <ds...@pivotal.io> wrote:

> Sure, you can have as many redundancy zones as you want.
>
> I'm don't think the redundancy zone setting affects quorum calculations.
> But if you can do something with the physical topology (3 different racks?)
> that makes it less likely to lose half of the members at once that might
> help.
>
> -Dan
>
>
> On Wed, Feb 10, 2016 at 9:49 AM, Michael Stolz <ms...@pivotal.io> wrote:
>
> > Is it possible to set up 3 separate redundancy zones so that a network
> > segmentation would have less chance of making the wrong decision about
> > quorum?
> >
> > --
> > Mike Stolz
> > Principal Engineer, GemFire Product Manager
> > Mobile: 631-835-4771
> >
>

Re: Three redundancy zones

[Dan Smith <ds...@pivotal.io>]

Sure, you can have as many redundancy zones as you want.

I'm don't think the redundancy zone setting affects quorum calculations.
But if you can do something with the physical topology (3 different racks?)
that makes it less likely to lose half of the members at once that might
help.

-Dan


On Wed, Feb 10, 2016 at 9:49 AM, Michael Stolz <ms...@pivotal.io> wrote:

> Is it possible to set up 3 separate redundancy zones so that a network
> segmentation would have less chance of making the wrong decision about
> quorum?
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: 631-835-4771
>