-
Notifications
You must be signed in to change notification settings - Fork 142
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
medusa verify failing because files do not exist #541
Comments
I really don't understand how these files could be missing, unless another process deleted them or the upload never really happened in the first place 🤯 |
We've shipped #716, so @adejanovski's suggestion basically got implemented. I'd propose closing this ticket because it reads like a duplicate of what we already did. |
This is very old, so I'm okay with closing it if you believe it's a duplicate and fixed. |
Project board link
First, this is happening with several nodes. For some reason, some nodes are good, but others keep failing. It's not just one backup either, it's any backup that gets created. We'll just use .108 to simplify though.
We have a manifest that shows the data exists on .108:
However, when we look at the bucket in s3, it does not exist:
It's an older sstable file, so is there something restricting based on time? The sstable no longer exists on disk, that's verified but it should exist in the backup.
When we do the verification, it's failing with:
There are more sstable files failing, but you get the gist.
Medusa.ini attached as medusa.txt.
Manifest.json attached as manifest.txt.
Medusa.log attached.
medusa.txt
manifest.txt
medusa-verify-stg1-iblock001-001.log
The text was updated successfully, but these errors were encountered: