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
otal.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-timeout (GEODE-3411)
>
> Hi there Aravind,
>
> I have a singular problem with this approach.
>
> If
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
neighbour JVM using neihbour's
member-timeout (GEODE-3411)
Hi, Aravind.
Can you help me understand why this might be a useful feature for Geode? I see
that your needs require it, but why would users in general want to allow longer
timeouts for some members? This is a significant change
, September 01, 2017 4:39 AM
To: dev@geode.apache.org
Subject: Re: DISCUSS : Monitor the neighbour JVM using neihbour's
member-timeout (GEODE-3411)
Hi, Aravind.
Can you help me understand why this might be a useful feature for Geode? I see
that your needs require it, but why would users in ge
Hi, Aravind.
Can you help me understand why this might be a useful feature for Geode? I
see that your needs require it, but why would users in general want to
allow longer timeouts for some members? This is a significant change with
backward-compatibility implications, so would be good for the c
Hi Team,
We have a requirement to configure different member timeout for different
members as we need some members to survive in the view for longer time than the
other the members before being kicked out of the view in case they aren't
responding.
1. Now with the current monitoring sy
Hi Team,
We have a requirement to configure different member timeout for different
members as we need some members to survive in the view for longer time than the
other the members before being kicked out of the view in case they aren't
responding.
1. Now with the current monitoring sy
15 matches
Mail list logo
