Hi Aaron,
I don't think we have such fine grained metrics on per operation state
size, but from your description that "YARN kills containers who are
exceeding their memory limits", I think the root cause is not the state
size but related to the memory consumption of the state backend.
My guess
Hi,
I’m not sure if there is some simple way of doing that (maybe some other
contributors will know more).
There are two potential ideas worth exploring:
- use periodically triggered save points for monitoring? If I remember
correctly save points are never incremental
- use save point
Hey Flink Community,
I'm working on a Flink application where we are implementing operators that
extend the RichFlatMap and RichCoFlatMap interfaces. As a result, we are
working directly with Flink's state API (ValueState, ListState, MapState).
Something that appears to be extremely valuable is
