Re: Delay in REST/UI readiness during JM recovery

:10 PM, Joey Echeverria mailto:jechever...@splunk.com>> wrote: I’m running Flink 1.5.0 in Kubernetes with HA enabled, but only a single Job Manager running. I’m using Zookeeper to store the fencing/leader information and S3 to store the job manager state. We’ve been running around 250 or so st

Re: Delay in REST/UI readiness during JM recovery

specifically have to wait for the dispatcher? 2) Is there a reason why the dispatcher can’t write the lock until after job recovery? 3) Is there anything I can/should be doing to speed up job recovery? Thanks! -Joey On Aug 2, 2018, at 9:24 AM, Joey Echeverria mailto:jechever...@splunk.com>>

Delay in REST/UI readiness during JM recovery

I’m running Flink 1.5.0 in Kubernetes with HA enabled, but only a single Job Manager running. I’m using Zookeeper to store the fencing/leader information and S3 to store the job manager state. We’ve been running around 250 or so streaming jobs and we’ve noticed that if the job manager pod is

Re: Delay in REST/UI readiness during JM recovery

Sorry to ping my own thread, but has anyone else encountered this? -Joey > On Jul 30, 2018, at 11:10 AM, Joey Echeverria wrote: > > I’m running Flink 1.5.0 in Kubernetes with HA enabled, but only a single Job > Manager running. I’m using Zookeeper to store the fencing/leader

Re: Delay in REST/UI readiness during JM recovery

d Chesnay who know this part of the implementation. Thanks, vino. 2018-08-03 11:09 GMT+08:00 Joey Echeverria mailto:jechever...@splunk.com>>: I don’t have logs available yet, but I do have some information from ZK. The culprit appears to be the /flink/default/leader/dispatcher_lo

Re: Delay in REST/UI readiness during JM recovery

inding these issues and creating them. Thanks, vino. 2018-08-07 8:18 GMT+08:00 Joey Echeverria mailto:jechever...@splunk.com>>: Thanks for the ping Vino. I created two JIRAs for the first two items: 1) https://issues.apache.org/jira/browse/FLINK-10077 2) https://issues.apache.org/jira/

Re: Flink Job Cluster Deployment on K8s

Try replacing the job.jar in the args in your helm chart with the classname for your job rather than the name of the jar file. -Joey On Oct 18, 2018, at 9:21 AM, Thad Truman mailto:ttru...@neovest.com>> wrote: Hello, I am trying to experiment with the new Flink job cluster on Kubernetes that

Re: Rich Function Thread Safety

I’ve seen a few mailing list posts (including this one) that say Flink guarantees there is no concurrent access to operator methods (e.g. flatMap, snapshotState, etc.) and thus synchronization isn’t needed when writing operators that support checkpointing. I was trying to find a place in the