[
https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823435#comment-15823435
]
Thomas Weise commented on APEXCORE-570:
---------------------------------------
Pramod, the process related discussion is now a thread on the mailing list. IMO
it is an opportunity to improvement, not to take offense. Your explanation
about how you arrive at your solution is very good and valuable. The problem is
that it remains only in your head unless you document it, which is what I asked
for yesterday.
"Yes, you are correct, the slowest subscriber will slow down the publisher
(unless it is parallel partition all the way through). But, this is expected
isn't it with back pressure."
Consider the case of two subscribers with same throughput but different
pattern. Once with constant and capped rate, other with bursts of activity. If
they are forced to read at the same rate, then both will be slower and overall
throughput reduce? Granted this is not the common scenario, but something to
consider.
> Prevent upstream operators from getting too far ahead when downstream
> operators are slow
> ----------------------------------------------------------------------------------------
>
> Key: APEXCORE-570
> URL: https://issues.apache.org/jira/browse/APEXCORE-570
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Pramod Immaneni
> Assignee: Pramod Immaneni
>
> If the downstream operators are slower than upstream operators then the
> upstream operators will get ahead and the gap can continue to increase.
> Provide an option to slow down or temporarily pause the upstream operators
> when they get too far ahead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
