[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953424#comment-16953424
]
Xintong Song commented on FLINK-14422:
--------------------------------------
[~lining],
I've updated the summary and description according to our offline discussion.
The original one seems a bit unclear. Please correct me if the updates are not
consistent with your original idea.
> Expose TaskExecutor resource configurations to RESTful API
> ----------------------------------------------------------
>
> Key: FLINK-14422
> URL: https://issues.apache.org/jira/browse/FLINK-14422
> Project: Flink
> Issue Type: Wish
> 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)
