Hi Vishwas,
The value of `env.java.opts` will be passed as JVM options to both jobmanager and taskmanager. Thus the same port is set for two processes.
If you need to pass JVM options to jobmanager and taskmanager differently, you can use `env.java.opts.jobmanager` and `env.java.opts.taskmanager`.
On Tue, Jul 9, 2019 at 4:41 AM Vishwas Siravara <
[hidden email]> wrote:
Hi guys,This is what my master and slave files look like
cat masters
localhost:8081
[was@sl73rspapd031 conf]$ cat slaves
localhost
The job manager comes up but the task manager does not, from the log file
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
This is because the job manager binds 5005 to its process and the task manager cannot do this since it is already associated with the
job manager, how can I start the task manager ? Should I comment out the debug config from the yaml file after job manager is up and start
the task manger separately ? Thanks for your help.