Hi Rad, the heap memory can only measured on a the JVM (Taskmanager/Jobmanager) level. If you have multiple jobs running in the same cluster, you can not separate their memory footprint easily unless you you only run Taskmanagers with a single Taskslot, so that one Taskmanager is always only executing a single job.
For the per JVM metrics, please check out this blogpost or the documentation [1,2] as a starting point. Best, Konstantin [1] https://flink.apache.org/news/2019/02/25/monitoring-best-practices.html [2] https://ci.apache.org/projects/flink/flink-docs-release-1.8/monitoring/metrics.html#memory On Mon, Apr 29, 2019 at 8:17 PM Rad Rad <radhya.sa...@gmail.com> wrote: > Hi, > > I would like to know the amount of heap memory currently used (in bytes) of > a specific job which runs on Flink cluster. > > Regards. > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ > -- Konstantin Knauf | Solutions Architect +49 160 91394525 Planned Absences: - <https://www.ververica.com/> Follow us @VervericaData -- Join Flink Forward <https://flink-forward.org/> - The Apache Flink Conference Stream Processing | Event Driven | Real Time -- Data Artisans GmbH | Invalidenstrasse 115, 10115 Berlin, Germany -- Data Artisans GmbH Registered at Amtsgericht Charlottenburg: HRB 158244 B Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
