Hi Vino,
Yeah, I mean node.
Thanks,
Deirdre
On Fri, Aug 31, 2018 at 12:13 AM vino yang wrote:
> Hi Deirdre,
>
> Usually, we don't recommend JM and TM in a container. @Chesnay, right? I
> want to confirm, is your container here meaning node?
>
> Thanks, vino.
>
> D
Or is there a way to specify in the command line to have the jm and tm run
in different containers on YARN?
On Thu, Aug 30, 2018 at 11:51 PM Deirdre Kong
wrote:
> @Chesnay, can you elaborate on how to map specific ports to a specific
> JM/TM process?
>
> @Vino, I can only updat
on YARN, then it seems that the way I said does not work.
> Maybe you specify a larger port range and will not cause conflicts.
> I am curious, why do you want to fix the run port of the reporter?
>
> Maybe you can expect Chesnay to give you advice.
>
> Thanks, vino.
>
&
ts.
>
> The issue you provided is handled by Chesnay, so maybe Chesnay opinion is
> more appropriate. Ping Chesnay for you.
>
> [1]:
> https://ci.apache.org/projects/flink/flink-docs-release-1.6/monitoring/metrics.html#prometheus-orgapacheflinkmetricsprometheusprometheusreporter
>
&g
Hi,
I am running Flink in Amazon EMR. In flink-conf.yaml, I have
`metrics.reporter.prom.port:
9249-9250`
Depending whether the job manager and task manager are running in the same
node, the task manager metrics are reported on port 9250 (if running on
same node as job manager), or on port 9249 (i
