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

[BUG]Replica health status is Connected when there is 0 connections #32861

Open
xinlian12 opened this issue Jan 10, 2023 · 1 comment
Open

[BUG]Replica health status is Connected when there is 0 connections #32861

xinlian12 opened this issue Jan 10, 2023 · 1 comment
Assignees
Labels
cosmos:v4-item Indicates this feature will be shipped as part of V4 release train Cosmos cosmos-java-ecosystem-dt-planning Considered for Dilithium semester planning

Comments

@xinlian12
Copy link
Member

Replica health status is connected when there is 0 connections. Two possibilities:

  1. Due to the idleEndpoint config, the connection has been closed
  2. Currently, for an idle connection, SDK only mark replica as unhealthy if the connection has been closed gracefully (FIN signal), if the connection has been closed unexpectedly, then SDK ignores it.

Proposal:
Mark replica as unhealthy if the connection is being closed unexpected. Needs test to verify.

@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jan 10, 2023
@xinlian12 xinlian12 added Cosmos and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jan 10, 2023
@ghost
Copy link

ghost commented Jan 10, 2023

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar, @TheovanKraay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cosmos:v4-item Indicates this feature will be shipped as part of V4 release train Cosmos cosmos-java-ecosystem-dt-planning Considered for Dilithium semester planning
Projects
None yet
Development

No branches or pull requests

4 participants