Chesnay, your solution is definitely the best approach. I was already
wondering why the decision was made to only support the UI through the
leading job manager only.
Jürgen, I don't think that your solution will work in our setup. We're
currently running 3 services, one for each job manager. We n
I think you can solve this already with a health check (health monitor
in OpenStack?).
I'm currently using GET requests to / and if they don't reply with a
200 code the LB
will not use them. Only the Leader answers with a 200 code whereas the
others send
a redirect with 30x code which should en
We intend to change the redirection behavior such that any jobmanager
(leading or not) can
accept requests, and communicates internally with the leader. In this
model you could setup
the flink.domain.tld to point to any jobmanager (or distribute requests
among them).
Would this work for you?
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
