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

Fix inverted expiry logic for DAS S3 backends #2600

Merged
merged 1 commit into from
Aug 21, 2024
Merged

Conversation

Tristan-Wilson
Copy link
Member

Also force a resync of all mirrors since if they were using S3, they may be missing data in S3.

Also force a resync of all mirrors since if they were using S3, they may
be missing data in S3.
@cla-bot cla-bot bot added the s Automatically added by the CLA bot if the creator of a PR is registered as having signed the CLA. label Aug 21, 2024
@PlasmaPower
Copy link
Collaborator

Doesn't this force a resync regardless of if the mirrors were using S3?

@Tristan-Wilson
Copy link
Member Author

Tristan-Wilson commented Aug 21, 2024

Doesn't this force a resync regardless of if the mirrors were using S3?

Yes it does. Resyncing Nova takes about a day, and the daserver can operate as normal while it's happening.

Copy link
Collaborator

@PlasmaPower PlasmaPower left a comment

Choose a reason for hiding this comment

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

LGTM

@PlasmaPower PlasmaPower merged commit 28310ae into master Aug 21, 2024
15 checks passed
@PlasmaPower PlasmaPower deleted the fix-s3-das-expiry branch August 21, 2024 19:13
PlasmaPower added a commit that referenced this pull request Aug 22, 2024
Fix inverted expiry logic for DAS S3 backends
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-approved s Automatically added by the CLA bot if the creator of a PR is registered as having signed the CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants