You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Terry Wang (Jira)" <ji...@apache.org> on 2020/05/25 09:10:00 UTC
[jira] [Commented] (FLINK-15848) Support both fixed allocator and
dynamic allocator in flink
[ https://issues.apache.org/jira/browse/FLINK-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115867#comment-17115867 ]
Terry Wang commented on FLINK-15848:
------------------------------------
+1 for this feature. It's very useful in benchmark and some other specific use case.
> 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: Major
>
> 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.3.4#803005)