-
Notifications
You must be signed in to change notification settings - Fork 432
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
backup-fetch has issues with specific parts of backups #1601
Comments
It's interesting that two of the parts (001 and 1666) happen at very different places in the output than expected. Also curious that the order of files seems to be mostly alphabetical, but zero padding is only used to 3 digits. I don't think it matters at all, but is a bit surprising. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Database name
PostgreSQL
Issue description
Describe your problem
When using backup-fetch to restore a backup, I consistently encounter errors on a few of the part files. These errors are printed out right after apparent success messages for each of those files. For example:
At the end, when using wal-g v2.0.1, it appears to indicate (with poor grammar) that the files failed to download, but are successful upon retry:
I'm not sure what might be special about these files, as they are not especially large, and I have no problem fetching them from S3 and untarring them manually. Our S3 is Ceph storage within the same location as the database nodes. Uncompressed sizes:
Please provide steps to reproduce
This is repeatable for me on any one of our backups, but I don't have any idea what the cause might be.
Please add config and wal-g stdout/stderr logs for debug purpose
The text was updated successfully, but these errors were encountered: