Hi,
I think there are a couple of potential explanations for the increased latency.
Let me point out two of the most obvious that come to my mind:
1) A state size of 20 MB sounds like something that could (completely or to a
large extend) fit into some cache layer of a modern CPU, whereas 200 M
Asking an additional question, what is the largest plan that the JobManager can
handle? Is there a limit? My flows don't need to run in parallel and can run
independently. I wanted them to run in one single job because it's part of one
logical commit on my side.
Thanks,
Regina
From: Chan, Regi
Hi
We're running 3 job managers in high availability cluster mode backed by
OpenStack/Openshift. We're currently exposing all 3 job managers using 3
different routes (flink-1.domain.tld, flink-2.domain.tld,
flink-3.domain.tld). When accessing the route for a job manager which isn't
the leader it a
I have a single node Flink instance which has the required jars for logback
in the lib folder (logback-classic.jar, logback-core.jar,
log4j-over-slf4j.jar). I have removed the jars for log4j from the lib
folder (log4j-1.2.17.jar, slf4j-log4j12-1.7.7.jar). 'logback.xml' is also
correctly updated in
I've created an issue on Jira and prepared pull request, here's the link:
https://github.com/apache/flink/pull/4924
Travis CI check is not passing but looks like it's not my fault :)
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
