flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Ewen <se...@apache.org>
Subject Re: Flink-1.0.0 JobManager is not running in Docker Container on AWS
Date Fri, 11 Mar 2016 13:23:32 GMT
Hi Deepak!

We can currently not split the bind address and advertised address, because
the Akka library only accepts packages sent explicitly to the bind address
(not sure why Akka has this artificial limitation, but it is there).

Can you bridge the container IP address to be visible from the outside?

Stephan


On Fri, Mar 11, 2016 at 1:03 PM, Ufuk Celebi <uce@apache.org> wrote:

> Hey Deepak!
>
> Your description of Flink's behaviour is correct. To summarize:
>
> # Host Address
>
> If you specify a host address as an argument to the JVM (via
> jobmanager.sh or the start-cluster.sh scripts) then that one is used.
> If you don't, it falls back to the value configured in flink-conf.yaml
> (what you describe).
>
> # Ports
>
> Default used random port and publishes via ZooKeeper. You can
> configure a port range only via recovery.jobmanager.port (what you
> describe).
>
> ---
>
> Your proposal would likely solve the issue, but isn't it possible to
> handle this outside of Flink? I've found this stack overflow question,
> which should be related:
>
> http://stackoverflow.com/questions/26539727/giving-a-docker-container-a-routable-ip-address
>
> What's your opinion?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message