----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/39605/ -----------------------------------------------------------
(Updated Oct. 27, 2015, 9:41 p.m.) Review request for geode, anilkumar gingade, Bruce Schuchardt, Jianxia Chen, and Lynn Gallinat. Repository: geode Description ------- It looks like the coordinator node has left, sent a leave message but the member that is supposed to become coordinator next, ignores this leave message (as he is not yet the coordinator). The fix is to not ignore these leave messages and instead have each member track them, similar to removedMembers list. When the leave message is processed by non coordinators, the results will be the same. However if the non coordinator will now become coordinator, they can now process these leave messages Diffs (updated) ----- gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/membership/NetView.java cb61a1b gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/membership/gms/fd/GMSHealthMonitor.java 774ab37 gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/membership/gms/membership/GMSJoinLeave.java 6d39a6a gemfire-core/src/test/java/com/gemstone/gemfire/distributed/internal/membership/gms/membership/GMSJoinLeaveJUnitTest.java 41b0df7 Diff: https://reviews.apache.org/r/39605/diff/ Testing ------- Ran precheckin but had a handful of failures due to suspect strings, will rerun Thanks, Jason Huynh
