Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(storage): remove most usage of max_committed_epoch #18641

Merged
merged 66 commits into from
Sep 29, 2024

Conversation

wenym1
Copy link
Contributor

@wenym1 wenym1 commented Sep 23, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Remove most usage of max_committed_epoch. Previously, the max_committed_epoch has the semantic as the committed epoch of all visible tables. In this PR, all previous usage of visible_table_committed_epoch is removed. The max_committed_epoch is only used meta node during recovery, to get the initial prev epoch after recovery. For this reason, the max_committed_epoch is exposed only via method max_committed_epoch_for_meta.

Notable changes in this PR:

  • The version() method of PinnedVersion is removed. Instead we use impl Deref<Target = HummockVersion> for PinnedVersion.
  • CN shared buffer will no longer maintain epoch watermark in sstable_object_id_manager.
  • In risectl, the max committed epoch will not be read or specified in the command.
  • The ConflictDetector is removed, which was not used previously.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Base automatically changed from yiming/per-table-try-wait-epoch to main September 27, 2024 05:34
@wenym1 wenym1 requested review from hzxa21, Li0k and zwang28 September 27, 2024 07:19
Copy link
Contributor

@zwang28 zwang28 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -73,7 +73,7 @@ impl MetaSnapshotMetadata {
id,
hummock_version_id: v.id,
ssts: v.get_object_ids(),
max_committed_epoch: v.visible_table_committed_epoch(),
max_committed_epoch: v.max_committed_epoch_for_meta(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The field max_committed_epoch can be removed too.
Unknown fields will be ignored when deserializing MetaSnapshotMetadata.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The field will be deprecated in #18644

@wenym1 wenym1 added this pull request to the merge queue Sep 29, 2024
Merged via the queue into main with commit d492843 Sep 29, 2024
31 of 33 checks passed
@wenym1 wenym1 deleted the yiming/no-frontend-max-committed-epoch branch September 29, 2024 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants