It is the membership coordinator that performs the final check on a
suspect member. If you have network partition detection enabled or are
using authentication of peers the role of membership coordinator will be
a locator (if one is in the system) so in your scenario it will be the
Locator that performs this check. It will use its own member-timeout to
determine how long to wait for a response to a "final check" message to
the suspected member.
If the Locator is down then the oldest member in the system will take
over the role. This might be server1 if the membership view is [ s1,
s2, s4, s3 ]. If there is a problem with s2 then s1 will use its own
member-timeout setting to determine how long to wait for a final-check
response from s1.
On 6/20/17 8:18 AM, Aravind Musigumpula wrote:
Hi,
Is there any way to configure different member-timeout for particular
jvm’s.
According to my understanding each jvm monitors its neighbor. If any
jvm is missing heart beat from its neighbor, it waits for
member-timeout interval and sends a suspect message. Then Coordinator
tries to contact that particular jvm, if it is unable to connect to
that jvm. Coordinator waits for its configured member-timeout interval
and removes that member if it is unable to connect to that jvm.
Scenario:
Locator: member-timeout=10000
Server1: member-timeout=20000
Server2: member-timeout=30000
Server3: member-timeout=20000
Server4: member-timeout=20000
Suppose server1 is monitoring server2. I made server2 stuck. So
server1 tries to contact the server2 , waits for 20000ms and sends
suspect message. Then locator tries to connect with server2 , if
unable to connect waits for 10000 and removes server3 from view.
My requirement is I don’t want to kick server2 until 40000ms. This can
be done by setting 30000 for the jvm which monitors server2. But how
can we see that this particular jvm monitors server2. In my case every
time different jvm is monitoring server2.
Please correct me if I am wrong.
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://www.amdocs.com/about/email-disclaimer
