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 check of clients from nodes #2936

Closed
sancar opened this issue Jul 8, 2014 · 1 comment · Fixed by #2965
Closed

Heartbeat check of clients from nodes #2936

sancar opened this issue Jul 8, 2014 · 1 comment · Fixed by #2965
Assignees
Labels
Source: Internal PR or issue was opened by an employee Team: Client Type: Defect
Milestone

Comments

@sancar
Copy link
Contributor

sancar commented Jul 8, 2014

We currently have a heartbeat check from clients so that clients can detect unresponsive nodes. Relying on same ping packets, we can implement a mechanism so that nodes will detect an unresponsive client. This way nodes can cleanup resources held by a client which is unresponsive or network is gone.

@sancar sancar self-assigned this Jul 8, 2014
@sancar sancar added this to the 3.3 milestone Jul 8, 2014
@noctarius
Copy link
Contributor

+1 like it :)

@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
devOpsHazelcast pushed a commit that referenced this issue Aug 12, 2024
)

Introduces `TestHazelcastInstanceFactory#newInstances[Parallel](int, IntFunction<Config>)`. In addition,
1. the Javadoc is improved, and
2. `createAddressOrNull(...)` and `checkElementsNotNull(...)` are moved below.

GitOrigin-RevId: 54080b0cbbefd46b91dd71c26f011d22113d443a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Team: Client Type: Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants