added stopwaitsecs value of 300 seconds to supervisord programs #206
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.
In order to stop and resume pruned nodes with supervisord, geth needs more time to gracefully shut down. We can achieve this be setting
stopwaitsecs
in thesupervisord.conf
file.If a value for
stopwaitsecs
isn't provided, the default value is 10 seconds. After this time has elapsed, supervisord will send aSIGKILL
to any remaining child processes. For nodes that have synced a few million blocks, 10 seconds is not enough time for flushing to disk, and geth is stopped withSIGKILL
. This results in incomplete/corrupt data, and the node will have to rewind and resync (often from genesis) when resumed. Increasingstopwaitsecs
solves this issue by giving the appropriate amount of time for the blockchain to flush to disk before stopping. This will not increase the amount of time it takes to successfully stop a node, as supervisord doesn't wait the full duration onceSIGCHLD
is received.