[
https://issues.apache.org/jira/browse/FLINK-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1400.
---------------------------------
Resolution: Won't Fix
This is expected behavior:
- A single task manager in local mode does not initialize the network data
exchange code (netty)
- To simulate a distributed setup locally, use the mini cluster and set the
number of task managers to > 1
- To simulate that in a standalone setup, start cluster with default values,
remove the PID file and start another taskmanager via the "taskmanager" script
> 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)
