Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed task retry #140

Closed
mingmwang opened this issue Aug 15, 2022 · 0 comments · Fixed by #261
Closed

Failed task retry #140

mingmwang opened this issue Aug 15, 2022 · 0 comments · Fixed by #261
Labels
enhancement New feature or request

Comments

@mingmwang
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant