To add one thing to Mesos question-
My assumption that constraints on JobManager can work, is based on the sentence from link bleow
“When running Flink with Marathon, the whole Flink cluster including the job manager will be run as Mesos tasks in the Mesos cluster.”
[Not sure this is accurate, since it seems to contradict the image in link below
Hi Till, group,
Thank you for your response.
After reading further online on Mesos – Can’t Mesos fill the requirement of running job manager in primary server?
By using: “constraints”: [[“datacenter”, “CLUSTER”, “main”]]
Is this supported by Flink cluster on Mesos ?
From: Till Rohrmann <trohrmann@xxxxxxxxxx>
that is an interesting use case you are describing here. I think, however, it depends mainly on the capabilities of ZooKeeper to produce the intended behavior. Flink itself relies on ZooKeeper for leader election in HA mode but does not expose any means to influence the leader election process. To be more precise ZK is used as a blackbox which simply tells a JobManager that it is now the leader, independent of any data center preferences. I'm not sure whether it is possible to tell ZooKeeper about these preferences. If not, then an alternative could be to implement one's own high availability services which does that at the moment.
On Mon, Jul 9, 2018 at 1:48 PM Sofer, Tovi <tovi.sofer@xxxxxxxx> wrote: