[
https://issues.apache.org/jira/browse/CASSANDRA-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006487#comment-17006487
] Michael Semb Wever commented on CASSANDRA-15292: ------------------------------------------------ ||branch||circleci||asf jenkins testall||asf jenkins dtests|| |[cassandra-3.0_15292|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/cassandra-3.0_15292]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.0_15292]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/42/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/42/]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/716/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/716]| |[cassandra-3.11_15292|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/cassandra-3.11_15292]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.11_15292]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/43/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/43/]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/717/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/717]| |[trunk_15292|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_15292]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Ftrunk_15292]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/44/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/44/]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/718/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/718]| > 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 > > 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]
