Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
WARNING: Client heartbeat is timed out , closing connection #8777
we have hazelcast cluster v3.6.4 deployed on aws,
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701
this message gets produced after we replace the client host , and logs gets polluted indefinitely
Aug 25, 2016 6:19:51 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
two nodes cluster
looks like other people have same issue as well - see in google groups
our server config:
not really a test. what happens, when we shutdown a client, one or more hazelcast members starts producing these messages indefinitely. So really, to reproduce it - start for example a 2 node cluster, add couple of clients, then remove a client, and add a new one. by the way we are running cluster in aws if that helps
Hello , I was able to recreate this issue using a very simple test code.
Hazelcast 3.7.1, some problem, get warning about a disconnected client of hours before, repeating indefinitely.
I was able to generate the case in this way:
Start server with the option:
Connect with C++ client while debugging, pause the process.
I see the repeated warning logs as described.