Post

2 followers Follow
0
Avatar

SUPECT Member Processing (GF 8.1.0)

Why are these SUSPECT messages filling up the logs files? I expected that the subject member to be kicked out after member-timeout elapsed? Seems like group membership is in an infinite loop. Also, operations such as rebalance is blocked during this condition.
[info 2016/01/05 11:41:38.613 EST <TimeScheduler.Thread> tid=0x1a] broadcasting SUSPECT message (suspected_mbrs=[10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400]) to group

[info 2016/01/05 11:41:43.613 EST <TimeScheduler.Thread> tid=0x1a] broadcasting SUSPECT message (suspected_mbrs=[10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400]) to group

[info 2016/01/05 11:41:43.614 EST <VERIFY_SUSPECT.TimerThread> tid=0x220] 10.23.36.129(EPM_CACHE_SERVER_DESKTOP1:54032)<v2>:11886: No suspect verification response received from 10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400 in 5000 milliseconds: I believe it is gone.

[info 2016/01/05 11:41:48.613 EST <TimeScheduler.Thread> tid=0x1a] broadcasting SUSPECT message (suspected_mbrs=[10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400]) to group

[info 2016/01/05 11:41:48.614 EST <VERIFY_SUSPECT.TimerThread> tid=0x220] 10.23.36.129(EPM_CACHE_SERVER_DESKTOP1:54032)<v2>:11886: No suspect verification response received from 10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400 in 5000 milliseconds: I believe it is gone.

[info 2016/01/05 11:41:53.613 EST <TimeScheduler.Thread> tid=0x1a] broadcasting SUSPECT message (suspected_mbrs=[10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400]) to group

[info 2016/01/05 11:41:53.615 EST <VERIFY_SUSPECT.TimerThread> tid=0x220] 10.23.36.129(EPM_CACHE_SERVER_DESKTOP1:54032)<v2>:11886: No suspect verification response received from 10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400 in 5000 milliseconds: I believe it is gone.

Joseph

Please sign in to leave a comment.

1 comment

0
Avatar

This member is suspecting member 10.23.36.129(EPM_CACHE_SERVER_DESKTOP2:50456)<v3>:35400, but that member is not getting kicked out for some reason. It would be interesting to see the logs for the coordinator (locator) and the member itself.

Barry Oglesby 0 votes