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.
---
