[jira] [Updated] (GEODE-3411) Do Final check based on suspected member-timeout.

[ 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-tim

[jira] [Updated] (GEODE-3411) Suspect a member by suspected member-timeout.

[ https://issues.apache.org/jira/browse/GEODE-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravind M updated GEODE-3411: - Summary: Suspect a member by suspected member-timeout. (was: Suspect the member by it's own member-timeou

[jira] [Updated] (GEODE-3411) Suspect the member by it's own member-timeout

[ https://issues.apache.org/jira/browse/GEODE-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravind M updated GEODE-3411: - Summary: Suspect the member by it's own member-timeout (was: Monitor the neighbour JVM using neihbour's m

[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 ] Aravind M updated GEODE-3411: - Description: The idea is able to make critical member to survive in the view for a little longer time tha

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16136386#comment-16136386 ] Aravind M commented on GEODE-3411: -- Thanks [~ukohlmeyer] for guiding me, I will share thi

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16131793#comment-16131793 ] Aravind M commented on GEODE-3411: -- Consider a scenario if there is a requirement where w

[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 ] Aravind M updated GEODE-3411: - Description: Now when a member monitor's its neighbor, It uses it's own member timeout to wait and then p

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

Aravind M created GEODE-3411: Summary: 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: W

[jira] [Commented] (GEODE-3052) Restarting 2 locators within 1s of each other causes potential locator split brain

[ https://issues.apache.org/jira/browse/GEODE-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047879#comment-16047879 ] Aravind M commented on GEODE-3052: -- Is the fix for this issue will be available on 1.2 re