[
https://issues.apache.org/jira/browse/FLINK-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716640#comment-14716640
]
Márton Balassi commented on FLINK-2499:
---------------------------------------
[~airbots] correct me if I am wrong but nohup.out is never created, because the
whole command is exxecuted through `ssh -n`, so the output that would go to
nohup.out actually goes to the commandline from which you invoke the start
script. Having a warning when a new daemon is started at a place where others
are already running would be very helpful, I am adding that.
> 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
> Assignee: Márton Balassi
>
> 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)
