Siva Gujju
05/21/2024, 9:09 PMKirill Ternovsky
05/21/2024, 9:50 PMRobert Young
05/21/2024, 9:53 PM./bin/start-cluster.sh ? Is the configuration default or has it been modified?Siva Gujju
05/22/2024, 1:12 AMRobert Young
05/22/2024, 1:31 AMjobmanager:
... snip ...
rpc:
# The external address of the host on which the JobManager runs and can be
# reached by the TaskManagers and any clients which want to connect. This setting
# is only used in Standalone mode and may be overwritten on the JobManager side
# by specifying the --host hostname parameter of the bin/jobmanager.sh executable.
# In high availability mode, if you use the bin/start-cluster.sh script and setup
# the conf/masters file, this will be taken care of automatically. Yarn
# automatically configure the host name based on the hostname of the node where the
# JobManager runs.
address: localhost
which configures the external address of the jobmanager. poking through the code it looks like it uses the rpc.address when it's attempting to connect to the blobserver.
So options could be to set job-manager bind-host to 0.0.0.0 so you are bound to all interfaces, including local. So it's connectable on localhost and your other interface.
Or try setting rpc.address to the same ip you are binding to.Robert Young
05/22/2024, 2:44 AMlocalhost here.
maybe there's some built in assumption that the JobManager can connect to itself on localhost, at least in this standalone configuration (even if you configure it to bind to a specific ip).Siva Gujju
05/22/2024, 12:18 PMRobert Young
05/22/2024, 8:57 PMrest:
address: 192.168.178.91
bind-address: 192.168.178.91
to bind the rest/web to a specific interface meant I can access the web UI on that interface and ./bin/flink run examples/batch/WordCount.jar succeeds.
Maybe easier if you could show your config.yaml