New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel TEARDOWN Is Delayed #1178
Comments
ChannelProcessingManager.receive(channelEvent) is currently synchronized. This is causing the channel starts and stops to happen sequentially. With the change to use dedicated threads (from thread pool) and changing the tuner channel source to block on shutdown, this is causing this timing issue to be more pronounced. Update the ChannelProcessingManager to move the locking down to a finer-grained level so that more events can be processed in parallel. |
…event handler to enable more fine-grained channel start/stop event processing. This was causing the channel start and stop events to occur sequentially.
…event handler to enable more fine-grained channel start/stop event processing. This was causing the channel start and stop events to occur sequentially. Adds stream processing with coordinated heartbeat.
…event handler to enable more fine-grained channel start/stop event processing. This was causing the channel start and stop events to occur sequentially. Adds stream processing with coordinated heartbeat. (#1185) Co-authored-by: Dennis Sheirer <dsheirer@github.com>
Channel teardown appears to be happening sequentially on a 2-second interval. It appears that when you have multiple channels that all need teardown at the same time, that they only teardown on a 2-second interval and sequentially, versus teardown as/when needed.
The text was updated successfully, but these errors were encountered: