You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2024/01/10 21:51:00 UTC
[jira] [Updated] (CASSANDRA-19260) org.apache.cassandra.tcm.ClusterMetadataService#commit does not catch up when rejected
[ https://issues.apache.org/jira/browse/CASSANDRA-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-19260:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Transient Incorrect Response(12987)
Complexity: Normal
Discovered By: Performance Regression Test
Fix Version/s: 5.x
Severity: Critical
Status: Open (was: Triage Needed)
> org.apache.cassandra.tcm.ClusterMetadataService#commit does not catch up when rejected
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19260
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19260
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
> Reporter: David Capwell
> Priority: Normal
> Fix For: 5.x
>
>
> This was found in the cep-15-accord branch (CASSANDRA-18804). The test that found this was a simple benchmark test.
> 1) deploy a 6 node cluster
> 2) create a table
> 3) in parallel launch many accord transactions
> When accord gets a transaction it needs to make sure the table is “managed” by accord which uses TCM for this bookkeeping, this is just a List<TableId> in ClusterMetadata. We found that we detect that the table isn’t managed so we try to add it, we get a reject and the TCM epoch has not moved forward!
> Debugging this it looks like org.apache.cassandra.tcm.RemoteProcessor#commit is the root cause as it only seems to try to catch up if there is a messaging error and not a TCM rejection! Given that the caller to TCM is not able to find the epoch to “wait” on I feel that this is a TCM issue as TCM normally tries to make sure success/rejects are blocking, but in this one case it appears not to be so
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org