Skip to content

Don't log invalid row for zero-token nodes - #519

Merged
dkropachev merged 1 commit into
scylladb:scylla-3.xfrom
dkropachev:dk/3.x-dont-log-invalid-row-for-zero-token-nodes
Apr 17, 2025
Merged

dkropachev merged 1 commit into
scylladb:scylla-3.xfrom
dkropachev:dk/3.x-dont-log-invalid-row-for-zero-token-nodes

Conversation

@dkropachev

@dkropachev dkropachev commented Apr 15, 2025 •

Copy link
Copy Markdown

In some cases having zero token node is a normal thing.
Logging invalid row each time driver updates metadata confuses users in such case and produce bad UX.

Fixes: #520

@dkropachev
dkropachev force-pushed the dk/3.x-dont-log-invalid-row-for-zero-token-nodes branch from a751fe3 to 417df63 Compare April 15, 2025 18:55
In some cases having zero token node is a normal thing.
Logging invalid row each time driver updates metadata confuses users in
such case and produce bad UX.
@dkropachev
dkropachev force-pushed the dk/3.x-dont-log-invalid-row-for-zero-token-nodes branch from 417df63 to 72e6dc2 Compare April 15, 2025 19:38
@dkropachev
dkropachev requested a review from Bouncheck April 16, 2025 17:26

@Bouncheck Bouncheck left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be the best to have a way to differentiate valid zero-token nodes from broken nodes that did not receive tokens, but afaik there is no way to do that.
LGTM, but note that now the driver will never warn about the second case.

@dkropachev
dkropachev merged commit d57e192 into scylladb:scylla-3.x Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants