Question2Replies578Views×Close popoverPradeep Chowdary Pydi (PradeepPydi) Anthem Senior PEGA DEVOPS and Cloud Administrator Anthem IN View Profile PradeepPydi Member since 2017 207 posts Anthem Posted: July 13, 2018Last activity: July 16, 2018Posted: 13 Jul 2018 17:54 EDTLast 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 [188.8.131.52]:5701 - 73d84999-9b1a-437b-abe1-b920f74d5432 has left cluster!PFA's for the logs. System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years agoPosted: 15 Jul 2018 23:28 EDT×Close popoverVenkata Chalapathi Janapati (janav) PEGA Principal Technical Solutions Engineer Pegasystems Inc. IN View Profilejanav PEGA replied to PradeepPydiHi, 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 Posted: 2 years agoPosted: 16 Jul 2018 0:33 EDT×Close popoverMahendra Kumar Mahaveer Chand (Mahendra_Kumar) Verizon Verizon IN View ProfileMahendra_Kumar Verizon replied to PradeepPydiHello, 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.