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

Mark node as down if unable to dial control conn #150

Merged
merged 1 commit into from
Oct 31, 2023

Conversation

sylwiaszunejko
Copy link
Collaborator

Previously if connection to the node failed, information about that was logged, but it was not handled in any other way. The node down handling has had been there, but it has had been deleted in apache@56d43d5.
If during restart the resources assigned to node change, the driver does not update this. That could lead to outdated information about shards.
In Scylla without this when restarting node with increased assigned resources happen, there was a panic due to wrong number of shards.
I added previously removed marking node as down.

Fixes: #145

Without this if during restart the resources assigned to node
change, the driver does not update this. That could lead to
outdated information about threads/shards.
@avelanarius avelanarius merged commit 0545682 into scylladb:master Oct 31, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants