Hi Sudharsan, The non-heap max is decided by JVM automatically and is not controlled by Flink. Moreover, it doesn't mean Flink will use up to that size of non-heap memory.
These metrics are fetched directly from JVM and do not correspond well with Flink's memory configurations, which very often lead to confusions. Since Flink-1.12, we have introduced a new web ui for the memory metrics, where the legacy metrics are preserved only for backward compatibility and are placed in an `Advanced` pane. I'd recommend ignoring them in 99% of the cases. Thank you~ Xintong Song On Fri, Jul 2, 2021 at 2:34 AM Sudharsan R <sud.r...@gmail.com> wrote: > Hi, > > On my flink setup, I have taskmanager.memory.process.size set to 2536M. I > expect all the memory components shown on the UI to add up to this number. > However, I don't see this. > > > I have flink managed memory: 811Mb > > JVM heap max: 886Mb > > JVM non-heap max: 744Mb > > Direct memory: 204Mb > > > This adds up to 2645Mb. Am i adding up things i should not be? > > Also, how was JVM non-heap max derived to be 744Mb? > > > Thanks > > Sudharsan > > >
