-
Notifications
You must be signed in to change notification settings - Fork 34
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
core, cmd, trie: pbss fix release v1.13.6 and v1.13.8 #618
Merged
huyngopt1994
merged 2 commits into
axieinfinity:path-base-implementing
from
Francesco4203:fix-release-v1.13.6
Nov 11, 2024
Merged
core, cmd, trie: pbss fix release v1.13.6 and v1.13.8 #618
huyngopt1994
merged 2 commits into
axieinfinity:path-base-implementing
from
Francesco4203:fix-release-v1.13.6
Nov 11, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Francesco4203
force-pushed
the
fix-release-v1.13.6
branch
4 times, most recently
from
November 5, 2024 04:53
95e34d7
to
af060c3
Compare
Francesco4203
force-pushed
the
fix-release-v1.13.6
branch
2 times, most recently
from
November 8, 2024 08:08
b7e22b7
to
64cabd1
Compare
Francesco4203
changed the title
core, cmd, trie: pbss fix release v1.13.6
core, cmd, trie: pbss fix release v1.13.6 and v1.13.8
Nov 8, 2024
This fixes a database corruption issue that could occur during state healing. When sync is aborted while certain modifications were already committed, and a reorg occurs, the database would contain incorrect trie nodes stored by path. These nodes need to detected/deleted in order to obtain a complete and fully correct state after state healing. --------- Co-authored-by: Felix Lange <[email protected]>
Original problem was caused by #28595, where we made it so that as soon as we start to sync, the root of the disk layer is deleted. That is not wrong per se, but another part of the code uses the "presence of the root" as an init-check for the pathdb. And, since the init-check now failed, the code tried to re-initialize it which failed since a sync was already ongoing. The total impact being: after a state-sync has begun, if the node for some reason is is shut down, it will refuse to start up again, with the error message: `Fatal: Failed to register the Ethereum service: waiting for sync.`. This change also modifies how `geth removedb` works, so that the user is prompted for two things: `state data` and `ancient chain`. The former includes both the chaindb aswell as any state history stored in ancients. --------- Co-authored-by: Martin HS <[email protected]>
Francesco4203
force-pushed
the
fix-release-v1.13.6
branch
from
November 9, 2024 11:00
8b4ed90
to
9d2dc76
Compare
let merge it. |
huyngopt1994
approved these changes
Nov 11, 2024
huyngopt1994
merged commit Nov 11, 2024
834da7f
into
axieinfinity:path-base-implementing
1 check passed
huyngopt1994
pushed a commit
that referenced
this pull request
Nov 21, 2024
* trie: remove inconsistent trie nodes during sync in path mode (#28595) This fixes a database corruption issue that could occur during state healing. When sync is aborted while certain modifications were already committed, and a reorg occurs, the database would contain incorrect trie nodes stored by path. These nodes need to detected/deleted in order to obtain a complete and fully correct state after state healing. --------- Co-authored-by: Felix Lange <[email protected]> * core, cmd, trie: fix the condition of pathdb initialization (#28718) Original problem was caused by #28595, where we made it so that as soon as we start to sync, the root of the disk layer is deleted. That is not wrong per se, but another part of the code uses the "presence of the root" as an init-check for the pathdb. And, since the init-check now failed, the code tried to re-initialize it which failed since a sync was already ongoing. The total impact being: after a state-sync has begun, if the node for some reason is is shut down, it will refuse to start up again, with the error message: `Fatal: Failed to register the Ethereum service: waiting for sync.`. This change also modifies how `geth removedb` works, so that the user is prompted for two things: `state data` and `ancient chain`. The former includes both the chaindb aswell as any state history stored in ancients. --------- Co-authored-by: Martin HS <[email protected]> --------- Co-authored-by: rjl493456442 <[email protected]> Co-authored-by: Felix Lange <[email protected]> Co-authored-by: Martin HS <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References: