Re: Fat jar fails deployment (streaming job too large)

-Original Message- > From: Niels [mailto:nielsdenis...@gmail.com <mailto:nielsdenis...@gmail.com>] > Sent: Tuesday, February 27, 2018 11:40 AM > To: user@flink.apache.org <mailto:user@flink.apache.org> > Subject: Re: Fat jar fails deployment (streaming job too large) > > H

Re: Fat jar fails deployment (streaming job too large)

In case it's useful I've found how to enable bit more debug logging on the jobmanager: flink_jobmanager_log.txt -- Sent from:

Re: Fat jar fails deployment (streaming job too large)

Hi Niels, the size of the jar does not play a role for Flink. What could be a problem is that the serialized `JobGraph` (user code with closures) is larger than 10 MB and, thus, exceeds the maximum default framesize of Akka. In such a case, it cannot be sent to the `JobMaster`. You can control

Re: Fat jar fails deployment (streaming job too large)

Hi Niels, There should be no size constraints on the complexity of an application or the size of a JAR file. The problem that you describe sounds a bit strange and should be fixed. Apparently, it has to spend more time on planning / submitting the application than before. Have you tried to

Fat jar fails deployment (streaming job too large)

Hi All, We've been using Flink 1.3.2 for a while now, but recently failed to deploy our fat jar to the cluster. The deployment only works when we remove 2 arbitrary operators, thus giving us the impression our job is too large. However, we only changed some case classes and serializers (to