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

Investigate and fix any unhandled error paths when removing wal files #25857

Open
praveen-influx opened this issue Jan 17, 2025 · 0 comments
Open
Labels

Comments

@praveen-influx
Copy link
Contributor

As part of the snapshotting process, currently wal files are removed leaving behind N wal files. Currently anything other than Generic are considered to be ok to move on. If it is a Generic error, there is a retry mechanism to keep trying until it is successful. It is not clear just on the surface what error types are mapped to Generic by object store. If there are intermittent connection failures do they end up as Generic error, if they do not then that needs to be handled separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant