[
https://issues.apache.org/jira/browse/GEODE-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297499#comment-16297499
]
ASF GitHub Bot commented on GEODE-3411:
---------------------------------------
bschuchardt commented on a change in pull request #1075: GEODE-3411 Do Final
check based on suspected member-timeout
URL: https://github.com/apache/geode/pull/1075#discussion_r157886429
##########
File path:
geode-core/src/main/java/org/apache/geode/distributed/internal/membership/NetView.java
##########
@@ -553,6 +554,18 @@ public String toString() {
// sb.append(ports[i]);
// }
sb.append("]");
+ sb.append(", MemberTimeouts : [");
Review comment:
Unfortunately this level of the system can't use member "names" as keys. A
member is not required to have a "name" in membership services. Each timeout
needs to be associated with an entry in the "members" list, similar to what's
done with failure detection ports.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Do Final check based on suspected member-timeout.
> -------------------------------------------------
>
> Key: GEODE-3411
> URL: https://issues.apache.org/jira/browse/GEODE-3411
> Project: Geode
> Issue Type: Wish
> Components: membership
> Reporter: Aravind M
>
> The idea is able to make critical member to survive in the view for a little
> longer time than others.
> But we cannot do with the current suspect mechanism.
> Now a member can be removed from the view in two cases: one is missing
> heartbeat and second is missing acknowledgement of message.
> In the first case ,the final check is done by coordinators member-timeout and
> in the second case the final check done by suspecting member by its own
> timeout.
> So, in these two cases if we manage to suspect the member by the
> member-timeout of the suspected one in the final check then we can achieve to
> make a member survive in the view a little longer by configuring a greater
> member-timeout to that member.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
