plugin/transfer: fix goroutine leak on axfr err #7516
Merged
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.
1. Why is this pull request needed and what does it do?
Fixes a goroutine leak in zone transfers: when a client disconnects (or
tr.Outerrors) mid-transfer, the server could return without draining the producer channel, leaving the producer goroutine blocked on a small buffer. This change drains the producer channel on client error, ensuring the producer completes and preventing leaks.Adds a unit test to verify the producer finishes after a simulated write failure. These tests fail against
master. Increases test coverage forplugin/transferfrom 67.5% to 70.7%.2. Which issues (if any) are related?
#6548
3. Which documentation changes (if any) need to be made?
None.
4. Does this introduce a backward incompatible change or deprecation?
No. The server now drains the producer channel to completion instead of leaking a goroutine.