[
https://issues.apache.org/jira/browse/CASSANDRA-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882514#comment-17882514
]
Michael Semb Wever edited comment on CASSANDRA-13704 at 9/17/24 9:11 PM:
-------------------------------------------------------------------------
New CI round after [~maedhroz]'s
[fix|https://github.com/apache/cassandra/pull/3544/commits/cf1918e9b621ccc8a90b4260489ce46f695bf6e1]:
- 5.0 profile "post-commit": [^CASSANDRA-13704_5-0_25_ci_summary.html] and
[^CASSANDRA-13704_5-0_25_results_details.tar.xz]
Three failures, all unrelated.
The failing tests were also run repeatedly locally (using CASSANDRA-18942),
previous failure rates were 1:4, now gone.
was (Author: michaelsembwever):
New CI round after [~maedhroz]'s
[fix|https://github.com/apache/cassandra/pull/3544/commits/cf1918e9b621ccc8a90b4260489ce46f695bf6e1]:
- 5.0 profile "post-commit": [^CASSANDRA-13704_5-0_25_ci_summary.html] and
[^CASSANDRA-13704_5-0_25_results_details.tar.xz]
Three failures, all unrelated.
> Safer handling of out of range tokens
> -------------------------------------
>
> Key: CASSANDRA-13704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13704
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Coordination, Legacy/Observability
> Reporter: Sam Tunnicliffe
> Assignee: Caleb Rackliffe
> Priority: Urgent
> Fix For: 4.0.x, 4.1.x, 5.0.x
>
> Attachments: CASSANDRA-13704_5-0_23_ci_summary.html,
> CASSANDRA-13704_5-0_23_results_details.tar.xz,
> CASSANDRA-13704_5-0_24_ci_summary.html,
> CASSANDRA-13704_5-0_24_results_details.tar.xz,
> CASSANDRA-13704_5-0_25_ci_summary.html,
> CASSANDRA-13704_5-0_25_results_details.tar.xz, ci_summary-1.html,
> ci_summary-2.html, ci_summary.html, result_details.tar-1.gz,
> result_details.tar-2.gz, result_details.tar.gz
>
> Time Spent: 7h 10m
> Remaining Estimate: 0h
>
> It is possible for nodes to have a divergent view of the ring, which can
> result in some operations being sent to the wrong nodes. This is an umbrella
> ticket to mitigate such issues by adding logging when a node is asked to
> perform an operation for tokens it does not own. This will be useful for
> detecting when the nodes' views of the ring diverge, which is not highly
> visible at the moment, and also for post-hoc analysis.
> It may also be beneficial to straight up reject certain operations, though
> this will need to balance the risk of performing those ops against the
> consequences rejecting them has on availability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
