geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-3411) Monitor the neighbour JVM using neihbour's member-timeout
Date Sun, 19 Nov 2017 07:31:01 GMT


ASF GitHub Bot commented on GEODE-3411:

aravindmusigumpula commented on issue #1075: GEODE-3411 Suspect the member by it's own member-timeout
instead of locator's.
   This is a new pull request for Geode-3411, the older one is

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:

> Monitor the neighbour JVM using neihbour's member-timeout
> ---------------------------------------------------------
>                 Key: GEODE-3411
>                 URL:
>             Project: Geode
>          Issue Type: Wish
>          Components: membership
>            Reporter: Aravind M
> Now when a member monitor's its neighbor, It uses it's own member timeout to wait and
then pass the suspect request to coordinator.
> But if we do so, while configuring the member timeout of all the member's, we are not
sure for how much time that member will be removed from the view as it depends on the member-timeout
of the jvm which is monitoring this one.
> So, if we use neighbor's member-timeout to wait for response instead of its own member-timeout,
then we can know for how much time a member will be removed from the view.

This message was sent by Atlassian JIRA

View raw message