[
https://issues.apache.org/jira/browse/FLINK-15037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15037:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Introduce LimittingMemoryManager as operator scope MemoyManager
> ---------------------------------------------------------------
>
> Key: FLINK-15037
> URL: https://issues.apache.org/jira/browse/FLINK-15037
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
