You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to reproduce #3549 noticed that a release_assert is hit, making the node to stop with an assert error.
This should be ideally changed so the node could detect it is running out of disk space, eventually triggering warnings for that. A graceful shutdown is preferred rather then letting it to fail on a success check write assertion.
Node version
V23.0DB3
Build details
Manually built.
OS and version
Ubuntu 20.04
Steps to reproduce the behavior
Ensure there is only a little of disk-space (50M) for the node to start running (it fails when there is no more disk-space).
Run a node instance.
Wait for it to stop working.
It hits a release assertion in the nano::write_mdb_txn::commit () method, at lmdb_txn.cpp:103
@zhyatt , the last change sent just improve the fail message, there aren't yet a previously sent warning or a graceful shutdown. Will let this for the issue #3551.
Summary
When trying to reproduce #3549 noticed that a release_assert is hit, making the node to stop with an assert error.
This should be ideally changed so the node could detect it is running out of disk space, eventually triggering warnings for that. A graceful shutdown is preferred rather then letting it to fail on a success check write assertion.
Node version
V23.0DB3
Build details
Manually built.
OS and version
Ubuntu 20.04
Steps to reproduce the behavior
nano::write_mdb_txn::commit ()
method, atlmdb_txn.cpp:103
Expected behavior
This scenario was only covered by an assertion.
Actual behavior
Hits the assertion and exits with a fail message.
Possible solution
Implement the solution proposed by: #3551
Supporting files
No response
The text was updated successfully, but these errors were encountered: