Persistence engineers, please correct me if I'm wrong: The diskStores
record membership view information and use this to figure out which
store is most up-to-date. When there is a split-brain there's no way to
know which is more recent.
Le 1/8/2016 8:34 AM, Michael Stolz a écrit :
I'm not sure I want to do wholesale defaults revision.
Yes this is a release that cannot be done in a rolling fashion, but it is
not (yet) a release that requires that pre-existing users to change their
settings in general to keep their current configuration.
I think it would be simple enough to supply a "recommended.properties" file
that sets things the way we now like them without actually changing the
hard-coded defaults.
I view the network-partition-detection property as a special case because
of its affect on diskstores which are automatically created if you use the
recommended serialization mechanism (pdx).
On the diskstore topic, if we know that the disk stores are wrong at
startup, why don't we just fix them? Why do we require user intervention?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Fri, Jan 8, 2016 at 11:13 AM, Real Wes Williams <[email protected]>
wrote:
What’s the level of concern here about members getting kicked out
prematurely depending on the newly proposed default settings? For
instance, if the default suspect notification is 3 seconds and they are
running in AWS or a mildly unpredictable network environment, a member
could be kicked out. What would be considered “safe” settings?
On Jan 7, 2016, at 4:18 PM, Bruce Schuchardt <[email protected]>
wrote:
Another thing that's been discussed for a long time is turning on
network-partition-detection by default. It is a major problem for someone
if a partition occurs and they are using persistence. The disk-stores on
all but one of the partitions have to be deleted and revoked.
