Skip to content

Re-check files the replica listings disagree on before reporting them - #13808

Merged
skettkepalli merged 1 commit into
EclipseFdn:aws-productionfrom
skettkepalli:fix/replica-check-persistence
Oct 6, 2026
Merged

skettkepalli merged 1 commit into
EclipseFdn:aws-productionfrom
skettkepalli:fix/replica-check-persistence

Conversation

@skettkepalli

Copy link
Copy Markdown
Contributor

The replica check compares two bucket listings that are taken minutes apart. When an extension is deleted in between, its files are still in the source listing but already gone from the copy, so the check reports them as missing and alerts, although both buckets are identical.

Files the listings disagree on are now checked again directly against S3: a file that no longer exists in the source was deleted, and one with the same ETag on both sides has caught up. Anything else, including a permission error, more than recheckMax files, or a bucket that does not answer, is still reported, and the names of files still missing go to the pod log.

This only changes the check job. It was tested in the job's image against a real case where 18 files of a deleted extension were reported missing, and against controls for a file missing from the copy and an unreachable bucket.

Signed-off-by: skettkepalli sridhar.ettkepalli@eclipse-foundation.org

Signed-off-by: skettkepalli <sridhar.ettkepalli@eclipse-foundation.org>
@skettkepalli
skettkepalli merged commit 8b05e4c into EclipseFdn:aws-production Oct 6, 2026
3 of 4 checks passed
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