[GitHub] [arrow-datafusion] edrevo opened a new issue #76: Make external hostname in executor optional

[GitBox <gi...@apache.org>]

edrevo opened a new issue #76:
URL: https://github.com/apache/arrow-datafusion/issues/76


   Having the ability to set an external/advertised hostname is great since it provides users a lot of flexibility in network deployments. However, having it a required argument is a pain for the most common scenario, where the scheduler, client and executors talk to each other in the same network (e.g. k8s or docker-compose).
   
   We should make the external hostname optional. If the scheduler receives executor metadata without a hostname, it should register the caller's IP address as the hostname.
   
   This will make it easier to deploy the executors as a kubernetes deployment, or to docker-compose scale ballista-executor=<N> in the integration tests.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-datafusion] andygrove closed issue #76: Make external hostname in executor optional

[GitBox <gi...@apache.org>]

andygrove closed issue #76:
URL: https://github.com/apache/arrow-datafusion/issues/76


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org