flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chesnay Schepler <ches...@apache.org>
Subject Re: JobManager web interface redirect strategy when running in HA
Date Wed, 01 Nov 2017 11:34:30 GMT
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?

I believe this is targeted for 1.5.

On 31.10.2017 13:55, mrooding wrote:
> 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 automatically redirects the user to the host and port of the
> leading job manager. From what I've seen in the source code the rpc address
> and port are being used to redirect. Since the internal hostnames are not
> accessible outside the cluster this obviously doesn't work.
>
> The nicest solution would be a single route (flink.domain.tld) which would
> correctly delegate requests to the leading job manager. The second best
> solution would probably be the possibility to declare a public URL in the
> flink configuration file.
>
> I'd be more than happy to contribute to Flink and add support for this but
> I'd love to hear your ideas about it.
>
> Kind regards
>
> Marc
>
>
>
>
> --
> Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
>


Mime
View raw message