[
https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468273#comment-17468273
]
ASF subversion and git services commented on GEODE-9060:
--------------------------------------------------------
Commit c9bb7644f210ed6d5a1f35de7dca45659e904a3c in geode's branch
refs/heads/support/1.14 from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9bb764 ]
GEODE-9060: Remove the member from a copy of replicates as GII candid… (#6246)
(#7230)
* GEODE-9060: Remove the member from a copy of replicates as GII candidate if
it's not part of the same distributed system, but leave original replicates
unchanged.
(cherry picked from commit 76a5afddc9eaecea9f0b4528a910eb6761e1a3a1)
> checkMyStateOnMemebers is better not to change the replicates
> -------------------------------------------------------------
>
> Key: GEODE-9060
> URL: https://issues.apache.org/jira/browse/GEODE-9060
> Project: Geode
> Issue Type: Bug
> Reporter: Xiaojian Zhou
> Assignee: Xiaojian Zhou
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> This is an enhancement to previous GEODE-9003.
> The previous fix will remove the members in replicates if it cannot recognize
> current member, thus these removed members will not acting as GII provider
> candidates. The fix is correct.
> However, Dan suggested to keep the replicates as is to be more conservative.
> These members will still act as GII provider candidates even they cannot
> recognize current member due to the split-brain. Conceptually these members
> should be the same as other online members.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
