[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468280#comment-17468280 ]
ASF subversion and git services commented on GEODE-9060: -------------------------------------------------------- Commit 1e2b384fdd43d6ddd5226d9b6fb18d88bb70fd98 in geode's branch refs/heads/support/1.12 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1e2b384 ] 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. (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.12.8, 1.13.7, 1.14.3, 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)