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

Rename S3 scrubber to storage scrubber #8013

Merged
merged 5 commits into from
Jun 11, 2024
Merged

Rename S3 scrubber to storage scrubber #8013

merged 5 commits into from
Jun 11, 2024

Conversation

arpad-m
Copy link
Member

@arpad-m arpad-m commented Jun 11, 2024

The S3 scrubber contains "S3" in its name, but we want to make it generic in terms of which storage is used (#7547). Therefore, rename it to "storage scrubber", following the naming scheme of already existing components "storage broker" and "storage controller".

Part of #7547

@arpad-m arpad-m requested a review from VladLazar June 11, 2024 15:08
Copy link

github-actions bot commented Jun 11, 2024

3198 tests run: 3056 passed, 0 failed, 142 skipped (full report)


Flaky tests (3)

Postgres 16

  • test_storage_controller_smoke: debug
  • test_subscriber_restart: release

Postgres 15

  • test_pageserver_restarts_under_worload: release

Code coverage* (full report)

  • functions: 31.6% (6626 of 20990 functions)
  • lines: 48.6% (51493 of 106045 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
357918b at 2024-06-11T21:41:05.264Z :recycle:

Copy link
Contributor

@VladLazar VladLazar left a comment

Choose a reason for hiding this comment

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

Looking at the code, the scrubber is S3 specific (it creates an s3 client). To my mind it would make more sense to make it generic first and rename it later. I don't mind too much though.

@arpad-m
Copy link
Member Author

arpad-m commented Jun 11, 2024

Yeah currently it's S3 specific in the implementation but I have done first steps in an open PR: #7932

We already use internally the new name, and I'd like the current/old name to not proliferate (and we are about to proliferate it further judging https://github.com/neondatabase/cloud/issues/14024 ).

Copy link
Contributor

@VladLazar VladLazar left a comment

Choose a reason for hiding this comment

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

I see no harm in merging this, but doing it now feels a bit awkward to me. In any case, feel free to merge.

test_runner/regress/test_s3_scrubber.py Show resolved Hide resolved
storage_scrubber/README.md Show resolved Hide resolved
@arpad-m arpad-m enabled auto-merge (squash) June 11, 2024 16:35
@arpad-m arpad-m merged commit 2751867 into main Jun 11, 2024
61 checks passed
@arpad-m arpad-m deleted the arpad/storage-scrubber branch June 11, 2024 22:45
VladLazar pushed a commit that referenced this pull request Jun 12, 2024
The S3 scrubber contains "S3" in its name, but we want to make it
generic in terms of which storage is used (#7547). Therefore, rename it
to "storage scrubber", following the naming scheme of already existing
components "storage broker" and "storage controller".

Part of #7547
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants