-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BACKPORT 2.6][#10504] docdb - Move value TTL metadata collection to …
…DocWriteBatch Summary: Request TTL metadata is currently missing from tablet replicas, leading to replica SST files missing value TTL frontier metadata necessary for expiration. This is happening because the metadata was being stored in operations (which are rebuilt on replicas) rather than being stored in the doc batch write requests themselves. This commit moves the value TTL metadata collection into DocWriteBatch and adds a field for ttl in the KeyValueWriteBatchPB. It also modifies the logic on the tablet side to calculate the expiration timestamp based on the KeyValueWriteBatchPB metadata. Also adds the CompactionTestWithFileExpirationRF3 test suite. Adjusted compaction-test.cc for 2.6 constructors Original commit: rYBDBbd2626d2b50f / D13855 Test Plan: Jenkins: hot Jenkins: rebase: 2.6 ybd --cxx-test integration-tests_compaction-test --gtest_filter CompactionTestWithFileExpiration.ReplicatedMetadataCanExpireFile ybd --cxx-test integration-tests_compaction-test --gtest_filter CompactionTestWithFileExpiration.ReplicatedNoMetadataUsesTableTTL ybd --cxx-test docdb_docdb-test --gtest_filter DocDBTests/DocDBTestWrapper.TestUpdateDocWriteBatchTTL/0 Reviewers: timur, rsami, sergei Reviewed By: sergei Subscribers: bogdan, anallan, ybase Differential Revision: https://phabricator.dev.yugabyte.com/D13927
- Loading branch information
Showing
8 changed files
with
175 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters