[
https://issues.apache.org/jira/browse/CASSANDRA-21646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-21646:
----------------------------------------
Bug Category: Parent values: Correctness(12982)
Complexity: Normal
Discovered By: User Report
Fix Version/s: NA
Severity: Normal
Status: Open (was: Triage Needed)
> CEP-45: Commit log and mutation journal positions conflict with each other
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-21646
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21646
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Normal
> Fix For: NA
>
>
> Writes to a table go to either the commit log or the mutation journal,
> depending on their replication type and migration status. Both record their
> position in the same CommitLogPosition type, but positions from the two logs
> are not comparable. Memtables and sstables use these positions to decide what
> has been persisted and what needs replay. Anything holding writes from both
> logs therefore records a bound that does not describe its contents.
> This is reachable in normal operation. Migrating a keyspace between untracked
> and tracked replication routes writes to both logs at once, and a commit log
> can be replayed after that migration has already finished.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
