[FLINK-15037] Introduce LimittingMemoryManager as operator scope MemoyManager

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.10.0
• Component/s: Runtime / Coordination
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Zhu Zhu
• Created: 03/Dec/19 11:05
• Updated: 20/Nov/21 22:38

Description

Current MemoryManager is slot scope component, and the operators needs to use a fraction to compute memory size/pages it can allocate and use it to reserver memory or allocate pages.
This, however, requires operators to be aware of the managed memory fraction. There is also risk that one operator may over allocate resources than it has declared and causes other operators to break.

To separate concerns, we can introduce a LimittingMemoryManager which wraps the the original MemoryManager but limit the available memory size to the fraction of total memory governed by the original one. This wrapper would be a operator scope MemoryManager.

Some more detailed discussions can be found in FLINK-14936.

cc azagrebin

Issue Links

• relates to: FLINK-14936 Introduce MemoryManager#computeMemorySize to calculate managed memory from a fraction