fix(ledger): prevent panic on snapshot manager shutdown #5380
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.
Type of change
Description
This PR fixes a shutdown race in the ledger snapshot manager that could cause a peer to panic.
Snapshot generation runs asynchronously in goroutines. If a peer shuts down while a snapshot is still in progress, those goroutines could attempt to send events on the events channel after it has been closed in shutdown(), resulting in a send on closed channel panic.
The fix coordinates snapshot goroutines with shutdown so that no sends occur after shutdown begins.
Additional details
Snapshot goroutines are now tracked and are signaled to stop during shutdown.
shutdown() waits for in-flight snapshot work to finish before closing channels.
Tested locally with
go test ./core/ledger/kvledger/...Release Note
Fixes a shutdown race in the ledger snapshot manager that could cause a peer
panic when snapshots are generated during shutdown.