Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heartbeat requests suddenly stopping to cluster members #153

Closed
rvenancio opened this issue Feb 8, 2018 · 2 comments
Closed

Heartbeat requests suddenly stopping to cluster members #153

rvenancio opened this issue Feb 8, 2018 · 2 comments

Comments

@rvenancio
Copy link

rvenancio commented Feb 8, 2018

The C# client (version 3.9.1) is connecting successfully to server nodes (also 3.9.1). After that, It starts sending heartbeat requests to the server nodes, but in about 2minutes it suddenly stops as we can see in the following logs.

2018-02-08 17:42:35.6516 |Debug ||||Sending heartbeat to Connection[0][IMember [10.131.22.75]:5712 -> 10.2.22.9:49375];
2018-02-08 17:42:35.6516 |Debug ||||Sending heartbeat to Connection[2][IMember [10.131.22.15]:5712 -> 10.2.22.9:49377];
2018-02-08 17:42:35.6516 |Debug ||||Sending heartbeat to Connection[4][IMember [10.2.22.43]:5712 -> 10.2.22.9:49379];
2018-02-08 17:42:35.8232 |Debug ||||Updating partition list.;
2018-02-08 17:42:35.8232 |Debug ||||Partition list updated;

2018-02-08 17:47:37.3372 |Warn ||||Got exception in connection Connection[0][IMember [10.131.22.75]:5712 -> 10.2.22.9:49375]:; Error message: Target[Address[10.
131.22.75]:5712] disconnected, Socket was closed.; Hazelcast.Client.Spi.TargetDisconnectedException: Target[Address[10.131.22.75]:5712] disconnected, Socket wa
s closed.
2018-02-08 17:47:37.3528 |Debug ||||Destroying connection Connection[0][IMember [10.131.22.75]:5712 -> 10.2.22.9:49375] due to Target[Address[10.131.22.75]:5712
] disconnected, Socket was closed.;

After 5minutes, the server nodes kick the client due to inactivity.

Anyone is also facing this issue?

@simpleusr
Copy link

Hi @rvenancio ,

It seems that we are facing the same or a similar issue?

#170

Did you find a solution?

Regards

@asimarslan
Copy link
Contributor

Duplicate issue. Closing this one and followup with #170

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants