[
https://issues.apache.org/jira/browse/FLINK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160581#comment-16160581
]
ASF GitHub Bot commented on FLINK-7521:
---------------------------------------
Github user zjureel commented on the issue:
https://github.com/apache/flink/pull/4654
@kl0u @zentol Thank you for your suggestions. So remove the code
`.addLast(new HttpObjectAggregator(100*1024*1024)` will be a temporary fix?
In fact it surprises me that the client sends the jar file of job to the
rest server instead of block file system, such as hdfs. As @zentol said, the
jars may be multiple 100mb large and we obviously can't allocate that much
memory in general, I think the client upload the jars to a block file system
may be a better way, or we should find a way to create a stream service in the
rest server and save the input stream of jar as soon as possible instead of
aggregate it in the memory. What do you think? thanks
> 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)
