You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Stop accepting new jobs. If a new job is submitted return an error indicating the scheduler is shutting down.
Continue to accept job status requests
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: