-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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/rawdb: use ro lock in readonly mode #28180
Conversation
Signed-off-by: jsvisa <delweng@gmail.com>
Signed-off-by: jsvisa <delweng@gmail.com>
Technically, I understand and can agree that it is "correct", in some manner, to allow several readers of the ancients. I don't think we should make our code more elaborate/complicated unless there's a compelling usecase to motivate it. |
For me, we have 2 nodes used as read-only partial-archive nodes( |
Co-authored-by: Martin Holst Swende <martin@swende.se>
This allows using the freezer from multiple processes at once in read-only mode. Co-authored-by: Martin Holst Swende <martin@swende.se>
This allows using the freezer from multiple processes at once in read-only mode. Co-authored-by: Martin Holst Swende <martin@swende.se>
This allows using the freezer from multiple processes at once in read-only mode. Co-authored-by: Martin Holst Swende <martin@swende.se>
This allows using the freezer from multiple processes at once in read-only mode. Co-authored-by: Martin Holst Swende <martin@swende.se>
core/rawdb: use readonly file lock in readonly mode (ethereum#28180) Conflicts: core/rawdb/freezer.go Conflict around our change from flock to NewFileLock. Accepted both. Additions: core/rawdb/fileutil{,_mock}.db: Added the now-used RLock to out interface, with a mock implementation for wasm.
No description provided.