Hi Juan >From our experience, you could check the jobmanager.log first to see whether >existing similar logs below:
max allowed size 128000 bytes, actual size of encoded class akka.actor.Status$Success was xxx bytes If you see these logs, you should increase the akka.framesize to larger value (default value is '10485760b') [1]. Otherwise, you could check the gc-log of job manager to see whether the gc overhead is too heavy for your job manager, consider to increase the memory for your job manager if so. [1] https://ci.apache.org/projects/flink/flink-docs-stable/ops/config.html#distributed-coordination-via-akka Apache Flink 1.6 Documentation: Configuration<https://ci.apache.org/projects/flink/flink-docs-stable/ops/config.html#distributed-coordination-via-akka> Key Default Description; jobmanager.heap.size "1024m" JVM heap size for the JobManager. taskmanager.heap.size "1024m" JVM heap size for the TaskManagers, which are the parallel workers of the system. ci.apache.org Best Yun Tang ________________________________ From: Juan Gentile <j.gent...@criteo.com> Sent: Wednesday, October 31, 2018 22:05 To: user@flink.apache.org Subject: 1.6 UI issues Hello! We are migrating the the last 1.6 version and all the jobs seem to work fine, but when we check individual jobs through the web interface we encounter the issue that after clicking on a job, either it takes too long to load the information of the job or it never loads at all. Has anyone had this issue? Any clues as to why? Thank you, Juan
