You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2017/09/15 21:46:00 UTC

[jira] [Updated] (GEODE-3411) Monitor the neighbour JVM using neihbour's member-timeout

     [ https://issues.apache.org/jira/browse/GEODE-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapnil Bawaskar updated GEODE-3411:
------------------------------------
    Fix Version/s:     (was: 1.3.0)

> Monitor the neighbour JVM using neihbour's member-timeout
> ---------------------------------------------------------
>
>                 Key: GEODE-3411
>                 URL: https://issues.apache.org/jira/browse/GEODE-3411
>             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
(v6.4.14#64029)