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.

Sign up for GitHub

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

Jump to bottom

Test that walproposer recovery is handled correctly #861

Closed
yeputons opened this issue Nov 10, 2021 · 2 comments · Fixed by neondatabase/postgres#147
Closed

Test that walproposer recovery is handled correctly #861

yeputons opened this issue Nov 10, 2021 · 2 comments · Fixed by neondatabase/postgres#147
Labels
c/storage/safekeeper Component: storage: safekeeper t/feature Issue type: feature, for new features or requests

Comments

@yeputons
Copy link
Contributor

See #859

For example, at the moment I'm not sure how exactly walproposer knows whether it's received enough WAL from a specific Safekeeper.
@yeputons yeputons added the t/feature Issue type: feature, for new features or requests label Nov 10, 2021
@kelvich
Copy link
Contributor

kelvich commented Jan 28, 2022

@arssher should we do anything here?

@kelvich kelvich added the c/storage/safekeeper Component: storage: safekeeper label Jan 28, 2022
@arssher
Copy link
Contributor

arssher commented Jan 28, 2022

yes, we should add a small check that all WAL was indeed received

@petuhovskiy petuhovskiy mentioned this issue Mar 31, 2022
Merged
@petuhovskiy petuhovskiy mentioned this issue Apr 5, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c/storage/safekeeper Component: storage: safekeeper t/feature Issue type: feature, for new features or requests
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Raise fatal error on failed recovery neondatabase/postgres
3 participants
@kelvich @yeputons @arssher