[
https://issues.apache.org/jira/browse/FLINK-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716882#comment-14716882
]
ASF GitHub Bot commented on FLINK-2499:
---------------------------------------
GitHub user mbalassi opened a pull request:
https://github.com/apache/flink/pull/1071
[FLINK-2499] [scripts] Warning message for hosts starting multiple da…
…emons
As per the discussion on the relevant
[ticket](https://issues.apache.org/jira/browse/FLINK-2499) adds a warning
message.
I decided against the latest comment of @StephanEwen on the issue, because
I have also run into (accidentally) trying to stack multiple JobManagers on the
same machine and it is nice to have this warning even in that case.
This solution is a bit too verbose in test setups with a lot of
TaskManagers on the same machine, but keeps the PID related code in the
`flink-daemon.sh`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mbalassi/flink FLINK-2499
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1071.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1071
----
commit 9a44340d3638faf9da1f3ca3073a415da689e065
Author: mbalassi <mbala...@apache.org>
Date: 2015-08-27T15:25:01Z
[FLINK-2499] [scripts] Warning message for hosts starting multiple daemons
----
> 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)
