flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yury Ruchin <yuri.ruc...@gmail.com>
Subject Re: Container JMX port setting / discovery for Flink on YARN
Date Fri, 25 Nov 2016 09:53:11 GMT
Thanks Stefan! I think this would help if I had just one container per
node. But that's not my case - there are multiple TaskManagers running on
the same node, so setting the same value will likely result in port
conflict.

2016-11-25 12:28 GMT+03:00 Stefan Richter <s.richter@data-artisans.com>:

> Hi,
>
> can you try adding the following to your flink.yaml?
>
> env.java.opts: -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=9999
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
>
> Best,
> Stefan
>
>
> > Am 24.11.2016 um 16:47 schrieb Yury Ruchin <yuri.ruchin@gmail.com>:
> >
> > Hi,
> >
> > I want to enable JMX for my Flink streaming app running in YARN session.
> How can I specify which ports containers will listen to? If I cannot
> control it (e. g. they will be chosen randomly) - how can I detect which
> ports were picked by containers: inspecting logs, looking at the Web UI
> etc.?
> >
> > Example: in Apache Storm it is easy to derive JMX port numbers from
> worker port (slot) numbers and pass it as a JVM argument to the worker
> start command, so that every slot is always associated with a stable and
> well-known JMX port.
> >
> > Any clue is appreciated. Thanks!
>
>

Mime
View raw message