Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Jul 13, 2018
Last activity: Jul 16, 2018
Posted: 13 Jul 2018 17:54 EDT
Last activity: 16 Jul 2018 0:33 EDT
Closed

com.hazelcast.core.MemberLeftException : Member has left cluster!

Hi Team,

Below mentioned error has been observed in the logs at the code import process has been getting failed.

2018-07-13 11:02:02,038 [erClockSynchDaemon-0] [ ] [ ] [ ] (anagement.internal.TimeChecker) ERROR - com.hazelcast.core.MemberLeftException: Member [ Proprietary information hidden]:5701 - 73d84999-9b1a-437b-abe1-b920f74d5432 has left cluster!

PFA's for the logs.

To see attachments, please log in.
System Administration

Posted: 6 years ago
Posted: 15 Jul 2018 23:28 EDT
Venkata Chalapathi Janapati (janav)
PEGA
Principal Engineer, Technical Support - Runtime Engine and Search
Pegasystems Inc.
IN

Hi,

Can you please check the cluster management landing page and see if you can find all your nodes in the cluster. Please let me know your observation.

Thanks,

Venkat

To see attachments, please log in.
Posted: 6 years ago
Posted: 16 Jul 2018 0:33 EDT
Mahendra Kumar Mahaveer Chand (Mahendra_Kumar)
Verizon

Verizon
IN

Hello, 

How many nodes do you have?.

Also there should be couple of lines more in the logs showing the exception due to which the member left the cluster. Share them.

You can check pr_sys_statusnodes table and check the status of the nodes. This exception can occur due to multiple reasons 

1. Issue with database connection or node is down.

2. The hazelcast port is not available. 

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice