Closed jkremser closed 6 years ago
if the master and workers have the DRIVER_HOST set to the service that points to the driver, it should fix the issue...
DRIVER_HOST
resources.yaml should provide some tips
workaround: in a notebook you can reconfigure the spark conf to see the driver
ouch, wrong repo, sorry I am closing this
if the master and workers have the
DRIVER_HOST
set to the service that points to the driver, it should fix the issue...resources.yaml should provide some tips
workaround: in a notebook you can reconfigure the spark conf to see the driver