Fix: transcoders wait forever on orchestrator restart #2705
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.
What does this pull request do?
Fixes a bug where transcoders would wait forever on a orchestrator restart if they had a previous transcoding session. Fix simply moves the
wg.Add(1)
call so that the wait group is able to reach0
againSpecific updates
My thinking is the bug got introduced in this commit: a1fb761#diff-0db7e4513a2e3eb16dedb22ed6a0920e6648e62733004c11dc0ed8a19f314464 so 0.5.34 should still be good, anything after that should have this issue
How did you test each of these updates
Ran a split O/T setup on my main Orchestrator and rebooted it while the connected transcoders were busy transcoding or recently completed a transcoding session. Repeated a couple of times and my transcoders reconnected successfully every time
Fix ran in a pool environment in production, all T's were able to restart themselves gracefully when restarting the O numerous times over the past few days!
Does this pull request close any open issues?
Fixes #2704