Blake Eggleston created CASSANDRA-21821:
-------------------------------------------
Summary: CEP-45: mutation tracking will cause entire commit log to
be replayed after an unclean restart
Key: CASSANDRA-21821
URL: https://issues.apache.org/jira/browse/CASSANDRA-21821
Project: Apache Cassandra
Issue Type: Bug
Reporter: Blake Eggleston
When restarting a node after a shutdown where the node was not drained, the
commit log replayer works out the minimum commit log position it needs to
replay by checking the replay position intervals on each of the sstables.
Tracked keyspaces don't store commit log positions though, so they'll either
return NONE (meaning replay the commit log from the beginning) or the last
replay position before being migrated to mutation tracking.
Unfortunately we can't use TCM state to figure out what to do because tcm
updates are in the commit log as well. So we need a method of letting commit
log replay know that it shouldn't consult a table for minimum replay position.
This would need to do the right thing for mutation tracking migration as well.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
