[
https://issues.apache.org/jira/browse/GEODE-6896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878189#comment-16878189
]
Dan Smith commented on GEODE-6896:
----------------------------------
[~eburghardt] and I tried to fix this issue, but it looks like we actually rely
on the current behavior in some of our tests.
Our attempt to change the behavior is here - we tried to go to all locators for
cluster configuration, not just locators with share configuration. Many tests
failed with this change.
https://github.com/upthewaterspout/geode/pull/new/feature/GEODE-6896-require-cluster-config
> Member can startup without cluster configuration if locator crashes on startup
> ------------------------------------------------------------------------------
>
> Key: GEODE-6896
> URL: https://issues.apache.org/jira/browse/GEODE-6896
> Project: Geode
> Issue Type: Bug
> Components: management
> Reporter: Dan Smith
> Priority: Major
> Attachments: GEODE-6896-test.diff
>
>
> Even if a user is actually using cluster configuration, it's possible for a
> member to start up without using the cluster configuration.
> If a locator crashes after a member joins the distributed system, but before
> it gets the cluster configuration, the member will just log a message and
> start up without cluster configuration in this check in GemFireCacheImpl
> {noformat}
> if (locatorsWithClusterConfig.isEmpty()) {
> logger.info("No locator(s) found with cluster configuration service");
> return null;
> }
> {noformat}
> This is especially problematic if persistent PDX is used, because the member
> will start up with a non persistent PDX region which will prevent any other
> members with persistence from starting up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
