[
https://issues.apache.org/jira/browse/FLINK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156740#comment-16156740
]
ASF GitHub Bot commented on FLINK-7521:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4654
This doesn't solve the problem of the JIRA. For the job submission we have
to send jars to the cluster, which may be multiple 100mb large; we obviously
can't allocate that much memory in general.
As @kl0u said, setting this value any higher (it is already _very_ high)
will cause insane memory consumption in the object aggregator in any case where
concurrent requests are in progress.
As such this isn't even a temporary fix, as this is not a viable fix for
the use-cases that are affected by the limit, so I'm afraid we'll have to
reject this PR.
> Remove the 10MB limit from the current REST implementation.
> -----------------------------------------------------------
>
> Key: FLINK-7521
> URL: https://issues.apache.org/jira/browse/FLINK-7521
> Project: Flink
> Issue Type: Bug
> Components: REST
> Affects Versions: 1.4.0
> Reporter: Kostas Kloudas
> Assignee: Fang Yong
> Priority: Blocker
> Fix For: 1.4.0
>
>
> In the current {{AbstractRestServer}} we impose an upper bound of 10MB in the
> states we can transfer. This is in the line {{.addLast(new
> HttpObjectAggregator(1024 * 1024 * 10))}} of the server implementation.
> This limit is restrictive for some of the usecases planned to use this
> implementation (e.g. the job submission client which has to send full jars,
> or the queryable state client which may have to receive states bigger than
> that).
> This issue proposes the elimination of this limit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
