[
https://issues.apache.org/jira/browse/FLINK-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101432#comment-16101432
]
ASF GitHub Bot commented on FLINK-7092:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/4289#discussion_r129522998
--- Diff:
flink-mesos/src/main/java/org/apache/flink/mesos/runtime/clusterframework/MesosResourceManager.java
---
@@ -312,6 +312,48 @@ private void recoverWorkers() throws Exception {
}
@Override
+ public void shutDown() throws Exception {
+ // shut down all components
+ if (taskMonitor != null) {
+ try {
+ actorSystem.stop(taskMonitor);
--- End diff --
We should try to gracefully stop the actors. I propose to use
`Patterns.gracefulStop`, then collecting for all actors the returned futures,
combining them and then wait on their completion with a timeout.
> Shutdown ResourceManager components properly
> --------------------------------------------
>
> Key: FLINK-7092
> URL: https://issues.apache.org/jira/browse/FLINK-7092
> Project: Flink
> Issue Type: Sub-task
> Components: Mesos
> Reporter: Till Rohrmann
> Priority: Minor
> Labels: flip-6
>
> The {{MesosResourceManager}} starts internally a {{TaskMonitor}},
> {{LaunchCoordinator}}, {{ConnectionMonitor}} and a
> {{ReconciliationCoordinator}}. These components have to be properly shut down
> when the {{MesosResourceManager}} closes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
