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)
When a task is failed on Ballista Executor, due to different failure reasons, sometimes the failed tasks need to be resubmitted to another Executor and rerun the failed tasks. Need to enhance the Ballista Scheduler to support this.
Need to enhance FailedTask rpc message to indicate whether the failure task should retry or not.
A good example of failed task that should retry is Executor lost. And on the other hand, user cancelled queries/tasks should not retry. A shuffle read failure should not retry the task either.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
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)
When a task is failed on Ballista Executor, due to different failure reasons, sometimes the failed tasks need to be resubmitted to another Executor and rerun the failed tasks. Need to enhance the Ballista Scheduler to support this.
Need to enhance
FailedTask
rpc message to indicate whether the failure task should retry or not.A good example of failed task that should retry is Executor lost. And on the other hand, user cancelled queries/tasks should not retry. A shuffle read failure should not retry the task either.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: