mtc_worker: Define shard3 #157
Merged
Conversation
This file contains hidden or 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
Member
|
What landmark base ID do we use here? How long do we keep the old shards around? |
Contributor
Author
The landmark ID doesn't need to be defined because it's not used by Azul anywhere. We could of course add the landmark ID and advertise it somewhere, either in the metadata API (e.g., https://bootstrap-mtca.cloudflareresearch.com/logs/shard2/metadata) or in the landmark API.
They're around indefinitely. To delete them, we would need to do a DO migration and manually delete the R2 bucket. This is probably the scope of a Change Request. |
bwesterb
approved these changes
Nov 11, 2025
cjpatton
force-pushed
the
cjpatton/shard3
branch
from
32b0920 to
02a5446
Compare
Contributor
Author
|
Rebased. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.