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

Understand the DB corruption caused by a failed state sync #8733

Closed
exalate-issue-sync bot opened this issue Mar 15, 2023 · 0 comments · Fixed by #8732
Closed

Understand the DB corruption caused by a failed state sync #8733

exalate-issue-sync bot opened this issue Mar 15, 2023 · 0 comments · Fixed by #8732
Assignees
@nikurt

Comments

@exalate-issue-sync
Copy link

No description provided.

@nikurt nikurt mentioned this issue Mar 15, 2023
Merged
near-bulldozer bot pushed a commit that referenced this issue Mar 16, 2023
@nikurt
fix: State Sync no longer corrupts the DB (#8732)
8ff99fe 
If a node gets stopped during State Sync then it fails to start due to an `unwrap()` on `send_network_chain_info()`. The state of the DB itself is fine. This PR makes the node gracefully handle that scenario and State Sync can safely resume and complete.

Fix: #8733
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nikurt nikurt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: State Sync no longer corrupts the DB nikurt/nearcore
1 participant
@nikurt