You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/01 22:39:00 UTC
[jira] [Commented] (GEODE-9060) checkMyStateOnMemebers is better
not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313464#comment-17313464 ]
ASF subversion and git services commented on GEODE-9060:
--------------------------------------------------------
Commit 76a5afddc9eaecea9f0b4528a910eb6761e1a3a1 in geode's branch refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=76a5afd ]
GEODE-9060: Remove the member from a copy of replicates as GII candid… (#6246)
* 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.
> 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
>
> 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.3.4#803005)