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.

Sign up for GitHub

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

Jump to bottom

awaitSchemaAgreement not ignoring ghost node #1736

Open
fesiqueira opened this issue Feb 1, 2024 · 1 comment · May be fixed by #1738
Open

awaitSchemaAgreement not ignoring ghost node #1736

fesiqueira opened this issue Feb 1, 2024 · 1 comment · May be fixed by #1738

Comments

@fesiqueira
Copy link

fesiqueira commented Feb 1, 2024 •
edited

Please answer these questions before submitting your issue. Thanks!

What version of Cassandra are you using?

3.11.11

What version of Gocql are you using?

v1.6.0

What version of Go are you using?

1.21.6

What did you do?

Running migrations that use WaitForSchemaAgreement

What did you expect to see?

The migrations to finish successfully

What did you see instead?

gocql: cluster schema versions not consistent: [<uuid1> <uuid2>]

Describe your Cassandra cluster

I have a cluster of 50+ nodes. One of them was replaced a few days ago but the system.peers was left in an inconsistent state, where the replaced node is still showing in there with a different schema_version.

The nodetool status command prints out the "correct" output, where the old node is NOT shown.

The system.peers table shows the old node and all columns are filled with some value, like:

peer         | rpc_address  | schema_version
10.100.XX.XX | 10.100.XX.XX | <uuid2>

The old node is unreachable.
@fesiqueira
Copy link
Author

I can work on a fix for it, but I'm not sure what to do to fix it. I know that drivers for Python and Java check the node state when asserting if a node is a valid peer.

@fesiqueira fesiqueira linked a pull request Feb 8, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ensure peer is up when waiting schema agreement fesiqueira/gocql
1 participant
@fesiqueira