Cool, good to hear!
It is one of those "it a feature, not a bug" situations ;-)
Flink's HA mode supports multiple masters, so the CLI needs to have a way
to find which master is "leader" (active, versus the passive masters on
standby). That discovery goes through ZooKeeper as well (which is the
Hey! It´s working now!!
I will do a summary for those who might have the same problem in the future:
- Flink 1.3.0 dockerized on Mesos:
- Add the HA configuration values in your flink app:
Hi Stephan,
So, do you mean to remove the “-m” param from the flink CLI call? And on the
other hand, that I should add the Zookeeper configuration in both sides, the
remote flink and locally in the flink CLI config, right?
Regards
On 31 Jul 2017, at 22:21, Stephan Ewen
Hi Francisco!
Can you drop the explicit address of the jobmanager? The client should pick
up that address automatically from ZooKeeper as well (together with the HA
leader session ID).
Please check if you have the ZooKeeper HA config entries in the config used
by the CLI.
Stephan
On Mon, Jul
Hi again,
On the other hand, we are running the following flink CLI command:
./flink run -d -m ${jobmanager.rpc.address}:${jobmanager.rpc.port}
${our-program-jar} ${our-program-params}
Maybe is the command what we are using wrongly?
Thank you
On 28 Jul 2017, at 11:07, Till Rohrmann
Hi Till,
Thanks for your answer.
We have reviewed the configuration and everything seems fine in our side… But
we´re still getting the message:
“Discard message
LeaderSessionMessage(----,SubmitJob(JobGraph(jobId:
041b67c7ef765c2f61bd69c2b9dacbce),DETACHED))
Hi Francisco,
have you set the right high-availability configuration options in your
client configuration as described here [1]? If not, then Flink is not able
to find the correct JobManager because it retrieves the address as well as
a fencing token (called leader session id) from the HA store
Hello,
We´re having lot of issues while trying to submit a job remotely using the
Flink CLI command line tool. We have tried different configurations but in all
of them we get errors from AKKA while trying to connect. I will try to
summarise the configurations we´ve tried.
- Flink 1.3.0
