wants to use the
>> existing behavior they will continue to use the same 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
day, 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 .
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
: 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: Ar
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@geode.apache.org
Subject: RE: Monitor the neighbour JVM using neihbour's member-timeout
Thanks Bruce for sugges
@geode.apache.org
Subject: RE: Monitor the neighbour JVM using neihbour's member-timeout
Thanks Bruce for suggestions, I will change the new variables from
InternalDistributedMember to NetView and do changes related to backward
compatibility.
Now I know that there is another way that membe
o:bschucha...@pivotal.io]
Sent: Thursday, September 07, 2017 10:42 PM
To: dev@geode.apache.org
Subject: Re: Monitor the neighbour JVM using neihbour's member-timeout
I think this might be an acceptable change though I doubt many people would
find it useful.
It's already possible to
I think this might be an acceptable change though I doubt many people
would find it useful.
It's already possible to set different member-timeouts on each node of
the distributed system but the meaning of the setting is the inverse of
what's proposed here, so having the current setting be diff
