[
https://issues.apache.org/jira/browse/FLINK-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15848:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Support both fixed allocator and dynamic allocator in flink
> -----------------------------------------------------------
>
> Key: FLINK-15848
> URL: https://issues.apache.org/jira/browse/FLINK-15848
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Affects Versions: 1.10.0
> Reporter: liupengcheng
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Currently, we removed static allocator and only support dynamic allocation in
> flink1.10, however, this allocator still has some drawbacks:
> # Can not allocate resources in a range, which means the resource usage is
> not under control, this has very bad effect in a shared resource cluster(e.g.
> Yarn), one big query or job may occupy all the resources and cause other
> jobs block.
> # Not support static resource allocation. That means we can hardly do
> benchmark testing across engines(e.g. Spark). Also, in resource shared
> cluster(e.g. Yarn) that support over-allocation, it's hard to align the
> resources usage.
> As discussed in FLINK-12362 , we should support both fixed allocator and
> dynamic allocator(dynamically allocating in a range) in flink.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
