-
Notifications
You must be signed in to change notification settings - Fork 74
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
Fan-out support for the same source #288
Comments
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
9 similar comments
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint. |
The multiplexer fans out one streaming store reader to different streaming queries.
This has efficiency of disk read / TFF deserialization, memory allocation etc.
But we may introduce new problems like one slow query processing pipeline will slow down other pipelines.
So it maintains some metrics for
channel
and detach the channel and its the pipeline when slowness is detected.Multiplexer is multiple-thread safe, and a multiplexer is bound to a shard
The text was updated successfully, but these errors were encountered: