[
https://issues.apache.org/jira/browse/FLINK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156701#comment-16156701
]
ASF GitHub Bot commented on FLINK-7521:
---------------------------------------
Github user kl0u commented on the issue:
https://github.com/apache/flink/pull/4654
Hi @zjureel ! Thanks for the work!
This can be a temporary fix, but I was thinking more of a long term one
where there is no limit.
The problems that I can find with such temporary solution are:
1) if we add this as a configuration parameter, and then remove it when we
have a proper fix, this may result in confusion for the users.
2) with this fix, the aggregator is going to allocate the specified limit
every time there is an element to parse, even though the element may be small.
This can be a waste of resources.
What do you think @zentol ?
> 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)
