[
https://issues.apache.org/jira/browse/FLINK-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797006#comment-16797006
]
Chesnay Schepler commented on FLINK-11914:
------------------------------------------
I think we have to be careful here. This would add a new kind of operations to
the REST API (cluster control), which realistically would have to be disabled
by default as I don't see many users being willing to expose a shutdown
button/call to their users.
Is this supposed to work in all deployment modes, or just YARN?
Conceptually, outside of standalone deployments, it should never be required
for users to manually shutdown TaskManagers. Shouldn't the container management
(in this case YARN) ensure that a single host is not overloaded? If it isn't
capable of doing so, what prevents YARN from allocating another TM on the same
host?
> Expose a REST endpoint in JobManager to kill specific TaskManager
> -----------------------------------------------------------------
>
> Key: FLINK-11914
> URL: https://issues.apache.org/jira/browse/FLINK-11914
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / REST
> Reporter: Shuyi Chen
> Assignee: Shuyi Chen
> Priority: Major
>
> we want to add capability in the Flink web UI to kill each individual TM by
> clicking a button, this would require first exposing the capability from the
> REST API endpoint. The reason is that some TM might be running on a heavily
> loaded YARN host over time, and we want to kill just that TM and have flink
> JM to reallocate a TM to restart the job graph. The other approach would be
> restart the entire YARN job and this is heavy-weight.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
