[
https://issues.apache.org/jira/browse/FLINK-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681926#comment-14681926
]
Chen He commented on FLINK-2499:
--------------------------------
+1, not only warning, we need to track each started TM so that we can stop
corresponding TM when we run stop-cluster.sh.
Another problem is using nohup command. Multiple TM using nohup, their output
interleaving each other, it is not a good way to debug. We should redirect to
TM.out instead of nohup.out. It also affect other nohup processes because they
all dump stdout to nohup.out
> start-cluster.sh can start multiple TaskManager on the same node
> ----------------------------------------------------------------
>
> Key: FLINK-2499
> URL: https://issues.apache.org/jira/browse/FLINK-2499
> Project: Flink
> Issue Type: Bug
> Affects Versions: 0.8.1
> Reporter: Chen He
>
> 11562 JobHistoryServer
> 3251 Main
> 10596 Jps
> 17934 RunJar
> 6879 Main
> 8837 Main
> 19215 RunJar
> 28902 DataNode
> 6627 TaskManager
> 642 NodeManager
> 10408 RunJar
> 10210 TaskManager
> 5067 TaskManager
> 357 ApplicationHistoryServer
> 3540 RunJar
> 28501 ResourceManager
> 28572 SecondaryNameNode
> 17630 QuorumPeerMain
> 9069 TaskManager
> If we keep execute the start-cluster.sh, it may generate infinite
> TaskManagers in a single system.
> And the "nohup" command in the start-cluster.sh can generate nohup.out file
> that disturb any other nohup processes in the system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
