[
https://issues.apache.org/jira/browse/FLINK-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705961#comment-15705961
]
ASF GitHub Bot commented on FLINK-5088:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/2883
I agree with the renaming you propose.
I would not allow `flush()` to override the capacity limit as this has the
potential to circumvent the capacity limit with a low latency `OutputFlusher`.
Should we keep the `tryFlush` and `flush` differentiation or replace `flush`
with `tryFlush`?
---
I've tested this on a cluster and didn't run into problems. Before merging,
I still need to add some unit tests though. Most probably, this will not make
it to 1.1.4.
> Add option to limit subpartition queue length
> ---------------------------------------------
>
> Key: FLINK-5088
> URL: https://issues.apache.org/jira/browse/FLINK-5088
> Project: Flink
> Issue Type: Improvement
> Components: Network
> Affects Versions: 1.1.3
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> Currently the sub partition queues are not bounded. Queued buffers are
> consumed by the network event loop or local consumers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
