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

Database corruption when downloading and stopping client #846

Closed
obscuren opened this issue May 1, 2015 · 0 comments
Closed

Database corruption when downloading and stopping client #846

obscuren opened this issue May 1, 2015 · 0 comments
Milestone

Comments

@obscuren
Copy link
Contributor

obscuren commented May 1, 2015

It's possible to corrupt the database while downloading and processing blocks because of an ungraceful shutdown of the protocol handler, downloader and chain manager.

@obscuren obscuren added this to the Frontier milestone May 1, 2015
@obscuren obscuren removed the type:bug label May 4, 2015
tony-ricciardi pushed a commit to tony-ricciardi/go-ethereum that referenced this issue Jan 20, 2022
…20573) (ethereum#846)

This is a temporary fix for a problem which started happening when the
dialer was changed to read nodes from an enode.Iterator. Before the
iterator change, discovery queries would always return within a couple
seconds even if there was no Internet access. Since the iterator won't
return unless a node is actually found, discoverTask can take much
longer. This means that the 'emergency connect' logic might not execute
in time, leading to a stuck node.

Co-authored-by: Felix Lange <fjl@twurst.com>
maoueh pushed a commit to streamingfast/go-ethereum that referenced this issue Jun 9, 2023
* rm : remove interruptctx from txsCh select case

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

No branches or pull requests

1 participant