[
https://issues.apache.org/jira/browse/FLINK-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276731#comment-14276731
]
Aljoscha Krettek commented on FLINK-1400:
-----------------------------------------
You can, with a hack. You start a cluster with one local TaskManager using
start-cluster.sh. Then you manually delete the pid file in the tmp directory
and start an additional TaskManager using task manager.sh.
On my machine I can use this to start a local cluster with 4 separate
TaskManagers:
{code}
flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/bin/start-cluster.sh
&& rm /tmp/flink-aljoscha-taskmanager.pid &&
flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/bin/taskmanager.sh
start && rm /tmp/flink-aljoscha-taskmanager.pid &&
flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/bin/taskmanager.sh
start && rm /tmp/flink-aljoscha-taskmanager.pid &&
flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/bin/taskmanager.sh
start
{code}
> In local mode, the default TaskManager won't listen on the data port.
> ---------------------------------------------------------------------
>
> Key: FLINK-1400
> URL: https://issues.apache.org/jira/browse/FLINK-1400
> Project: Flink
> Issue Type: Bug
> Affects Versions: 0.9
> Environment: Ubuntu 14.04 LTS
> Reporter: Sergey Dudoladov
> Priority: Minor
>
> The Task Manager automatically started by the Job Manager (JobManager.scala,
> appr. line 470) in the local mode does not listen on the dataport.
> To reproduce:
> 1) Start Flink via ./start-local.sh
> 2) Look up the data port number on locahost:8081 -> "Task Managers" tab
> 3) sudo netstat -taupen | grep "dataport_number "
>
> Or start the second Task Manager and run Flink with the degree of
> parallelism 2 (assuming one slot per Task Manager)
> 4) ./flink run -p 2 ...
> Task Managers started via ./taskmanager.sh work fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
