[
https://issues.apache.org/jira/browse/FLINK-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180418#comment-16180418
]
Till Rohrmann commented on FLINK-7648:
--------------------------------------
Hi [~phoenixjiangnan], this one is indeed one of the more complex handlers,
because there are still things missing on the {{ResourceManager}} side.
In a nutshell:
- We have to register the {{HardwareInformation}} for each {{TaskExecutor}} at
the {{ResourceManager}} to answer the request
- We have to add a {{LeaderGatewayRetriever<ResourceManager>}} to this handler
to be able to talk to the {{ResourceManager}}
You can test the web gui by either starting a Flip-6 local cluster via
`bin/start-cluster.sh flip6` or by starting the
`StandaloneSessionClusterEntrypoint` with `flink-runtime-web` in its classpath.
Testing the handler itself should be quite simple. Just write a junit test. The
integration would be a bit more involved by spawning a RM which can serve the
TM information.
If this should be too involved, then I would recommend starting with the
metrics handlers ({{AbstractMetricsHandler}}).
> Port TaskManagersHandler to new REST endpoint
> ---------------------------------------------
>
> Key: FLINK-7648
> URL: https://issues.apache.org/jira/browse/FLINK-7648
> Project: Flink
> Issue Type: Sub-task
> Components: REST, Webfrontend
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Bowen Li
> Labels: flip-6
> Fix For: 1.4.0
>
>
> Port existing {{TaskManagersHandler}} to the new REST endpoint
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
