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

ui: node reconnection events confused with "dead" node events #61562

Closed
dhartunian opened this issue Mar 5, 2021 · 2 comments
Closed

ui: node reconnection events confused with "dead" node events #61562

dhartunian opened this issue Mar 5, 2021 · 2 comments
Assignees
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@dhartunian
Copy link
Collaborator

dhartunian commented Mar 5, 2021

Describe the problem

From customer:

I deployed docker images of cockroach and all nodes are connected. But I see duplicate nodes in the admin UI.
For some reason of network issue/deployment problem, 3 of the nodes got disconnected and admin UI displayed these as dead.
When network is restored, these 3 nodes are restarted. Then these nodes got added and admin UI displayed that these are healthy. But the problem is those same nodes which are restarted are shown twice in admin UI, once as dead and other as healthy with exactly identical IP:PORT (only node number varies). So let’s say, instead of 10 nodes admin UI displays total nodes as 13 and shows 3 as dead. But those 3 dead ones became healthy after restarting.

To Reproduce

Expected behavior
A clear and concise description of what you expected to happen.

Additional data / screenshots
If the problem is SQL-related, include a copy of the SQL query and the schema
of the supporting tables.

If a node in your cluster encountered a fatal error, supply the contents of the
log directories (at minimum of the affected node(s), but preferably all nodes).

Note that log files can contain confidential information. Please continue
creating this issue, but contact [email protected] to submit the log
files in private.

If applicable, add screenshots to help explain your problem.

Environment:

  • CockroachDB version [e.g. 2.0.x]
  • Server OS: [e.g. Linux/Distrib]
  • Client app [e.g. cockroach sql, JDBC, ...]

Additional context
What was the impact?

Add any other context about the problem here.

Jira issue: CRDB-2996

@dhartunian dhartunian added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-observability labels Mar 5, 2021
@dhartunian
Copy link
Collaborator Author

Possibly related to: #59322 and #58026 and #50707 and #50309

@thtruo
Copy link
Contributor

thtruo commented Mar 8, 2022

Closing this issue as we have not been able to reproduce the issue. KV Observability will continue to address the related issues tagged in the previous comment

@thtruo thtruo closed this as completed Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

No branches or pull requests

4 participants