[
https://issues.apache.org/jira/browse/CASSANDRA-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-15292:
-------------------------------------------
Fix Version/s: (was: 3.11.x)
(was: 4.x)
(was: 3.0.x)
4.0-alpha
3.11.6
3.0.20
Source Control Link:
https://github.com/apache/cassandra/commit/577a9e34f5ed28640c5abe4476f094c2ad2c51aa
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as 577a9e34f5ed28640c5abe4476f094c2ad2c51aa
> Point-in-time recovery ignoring timestamp of static column updates
> ------------------------------------------------------------------
>
> Key: CASSANDRA-15292
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15292
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Commit Log
> Reporter: Vincent White
> Priority: Normal
> Fix For: 3.0.20, 3.11.6, 4.0-alpha
>
>
> During point-in-time recovery
> org.apache.cassandra.db.partitions.PartitionUpdate#maxTimestamp is checked to
> see if any write timestamps in the update exceed the recovery point. If any
> of the timestamps do exceed this point the the commit log replay is stopped.
> Currently maxTimestamp only iterates over the regular rows in the update and
> doesn't check for any included updates to static columns. If a ParitionUpdate
> only contains updates to static columns then maxTimestamp will return
> Long.MIN_VALUE and always be replayed.
> This generally isn't much of an issue, except for non-dense compact storage
> tables which are implemented in the 3.x storage engine in large part with
> static columns. In this case the commit log will always continue applying
> updates to them past the recovery point until it hits an update to a
> different table with regular columns or reaches the end of the commit logs.
>
> ||Patch||
> |[3.11|https://github.com/vincewhite/cassandra/commits/3_11_check_static_column_timestamps_commit_log_archive]|
> |[Trunk|https://github.com/vincewhite/cassandra/commits/trunk_check_static_column_timestamps]|
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]