thinkharderdev opened a new issue, #565:
URL: https://github.com/apache/arrow-ballista/issues/565
**Is your feature request related to a problem or challenge? Please describe
what you are trying to do.**
A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
(This section helps Arrow developers understand the context and *why* for
this feature, in addition to the *what*)
We currently have graceful shutdown for the Ballista executors. We should
have a similar behavior for the scheduler.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
When the scheduler process receives a SIGTERM (or the equivalent on
non-Linux), it should initiate a graceful shutdown. This would consist of:
1. Stop accepting new jobs. If a new job is submitted return an error
indicating the scheduler is shutting down.
2. Continue to accept job status requests
3. Do not shutdown until either
i. All active jobs on the scheduler are completed
ii. Some configured timeout (default 30s?) elapses
This could be extended in the future to try and "hand off" scheduling to
other schedulers but that is not necessary for now.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features
you've considered.
We could do nothing
**Additional context**
Add any other context or screenshots about the feature request here.
--
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]
