You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lining (Jira)" <ji...@apache.org> on 2019/12/19 10:42:00 UTC
[jira] [Updated] (FLINK-14422) Add metric for shuffle memory
[ https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lining updated FLINK-14422:
---------------------------
Summary: Add metric for shuffle memory (was: Expose TaskExecutor resource configurations to rest api)
> Add metric for shuffle memory
> -----------------------------
>
> Key: FLINK-14422
> URL: https://issues.apache.org/jira/browse/FLINK-14422
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
> Reporter: lining
> Priority: Major
>
> TaskExecutors in the same Flink cluster might be configured with different resources. It would be helpful to expose TaskExecutors' resource configs to RESTful API, so it can be displayed on Flink web ui or queried by external systems.
> Currently, resource configurations are used for creating TaskExecutorServices, which will be passed into the TaskExecutor. The TaskExecutor, after created, is not aware of its resource configuration.
> We propose to also pass the original resource configs into the TaskExecutor, and report it to ResourceManager on registration. In that way, the rest server can acquire the resource configs from ResourceManager, as part of TaskManagerInfo.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)