[
https://issues.apache.org/jira/browse/FLINK-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275813#comment-14275813
]
Robert Metzger commented on FLINK-1400:
---------------------------------------
Hi,
thank you for reporting the issue.
I think when starting flink with "start-local.sh", all services of Flink
(JobManager and TaskManager) are started within one JVM. So we don't start any
network / RPC services for that (data is transported via memory).
The only ports which are opened in that case are the JobManager's web interface
on port 8081.
When starting TaskManagers using "./taskmanager.sh", the TMs and the JM run in
different JVMs. Since you then also need to exchange data, the components will
start the required network services.
> 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)
