[
https://issues.apache.org/jira/browse/FLINK-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702221#comment-15702221
]
ASF GitHub Bot commented on FLINK-5088:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2883
Since the capacity limit refers both to input and output queues, we should
probably rename `taskmanager.net.max-out-queue-length` to
`taskmanager.net.max-queue-length`.
> 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)
