RE: Monitor the neighbour JVM using neihbour's member-timeout

Hi Community, Any Comments on the below one. Thanks, Aravind Musigumpula -Original Message- From: Bruce Schuchardt [mailto:bschucha...@pivotal.io] Sent: Thursday, January 18, 2018 11:58 PM To: dev@geode.apache.org Subject: Re: Monitor the neighbour JVM using neihbour's m

RE: Monitor the neighbour JVM using neihbour's member-timeout

member-timeouts for all the nodes. So the behavior of the system is preserved. If you have any concerns in this solution, please let me know. Thanks, Aravind Musigumpula -Original Message- From: Aravind Musigumpula Sent: Monday, December 18, 2017 6:55 PM To: dev@geode.apache.org Subject

RE: Monitor the neighbour JVM using neihbour's member-timeout

Hi Community, Can you please give your suggestions on the below solution. I have raised a pull request for the same : https://github.com/apache/geode/pull/1075 . Thanks, Aravind Musigumpula -Original Message- From: Aravind Musigumpula Sent: Friday, November 03, 2017 3:23 PM To: dev

RE: Monitor the neighbour JVM using neihbour's member-timeout

t uses the suspected member-timeout(which is a greater value). The final check is common place in both the no heartbeat scenario and no response for a message scenario. Are there any concerns around this new proposal ? Thanks, Aravind Musigumpula -Original Message- From: Bruce Schuchardt [mailt

RE: DISCUSS : Monitor the neighbour JVM using neihbour's member-timeout (GEODE-3411)

member timeout for all the members. Thanks, Aravind Musigumpula -Original Message- From: Udo Kohlmeyer [mailto:ukohlme...@pivotal.io] Sent: Friday, September 01, 2017 10:05 PM To: dev@geode.apache.org Subject: Re: DISCUSS : Monitor the neighbour JVM using neihbour's member-time

RE: DISCUSS : Monitor the neighbour JVM using neihbour's member-timeout (GEODE-3411)

Hi Brian, This will help if the user has some member doing a heavy duty when compared to others, in this case we need to give such member some extra time to that member. Thanks, Aravind Musigumpula -Original Message- From: Brian Baynes [mailto:bbay...@pivotal.io] Sent: Friday

DISCUSS : Monitor the neighbour JVM using neihbour's member-timeout (GEODE-3411)

he above approach correct? Do we have any concerns around this area? Please give your insights on this issue. Thanks, Aravind Musigumpula This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://w

Monitor the neighbour JVM using neihbour's member-timeout

he above approach correct? Do we have any concerns around this area? Please give your insights on this issue. Thanks, Aravind Musigumpula This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://w

RE: Different member-timeout for particular jvm’s

timeout to monitor s4, then we can determine for how much time a member will be removed from the view. Is there any way to get the member timeout of one member from an another ? Thanks, Aravind Musigumpula From: Aravind Musigumpula Sent: Monday, July 03, 2017 9:35 PM To: u...@geode.apache.org

RE: Geode Exception: cluster configuration service not available

:+PrintGCApplicationConcurrentTime -J-XX:+PrintGCApplicationStoppedTime Initially it was set to true as it was not working I set it to false and tried, but it also didn’t work. Thanks, Aravind Musigumpula -Original Message- From: Jinmei Liao [mailto:jil...@pivotal.io] Sent: Wednesday

Geode Exception: cluster configuration service not available

Hi, I am using a cluster configuration in geode 1.1.1 . I am starting two locators on different hosts and one server for each locator. When I stop them and restart the cluster, I can see that in one of the locator view , it is receiving only one locator. In gfsh list members, I can see only on