onthebridgetonowhere commented on code in PR #329:
URL: https://github.com/apache/arrow-ballista/pull/329#discussion_r996251873
##########
docker-compose.yml:
##########
@@ -54,8 +54,7 @@ services:
volumes:
- ./benchmarks/data:/data
depends_on:
- ballista-scheduler:
- condition: service_healthy
Review Comment:
@andygrove - I am not too familiar with the codebase yet, but I saw that if
the scheduler is killed while executor is running, the executor tries to
reconnect forever. Once the scheduler is restarted, the executor is fine.
Probably a silly question, but couldn't this behaviour be there from the start?
Why does it first need to connect to an actual running instance of the
scheduler, instead of keep trying the default/configured one until it succeeds?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
