geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravind M (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-3411) Do Final check based on suspected member-timeout.
Date Tue, 21 Nov 2017 09:05:00 GMT

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

Aravind M updated GEODE-3411:
-----------------------------
    Summary: Do Final check based on suspected member-timeout.  (was: Suspect a member by
suspected member-timeout.)

> 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)

Mime
View raw message