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

Don't throw error when job path not exist in remove_job_data #502

Closed
yahoNanJing opened this issue Nov 8, 2022 · 0 comments · Fixed by #503
Closed

Don't throw error when job path not exist in remove_job_data #502

yahoNanJing opened this issue Nov 8, 2022 · 0 comments · Fixed by #503
Labels
enhancement New feature or request

Comments

@yahoNanJing
Copy link
Contributor

yahoNanJing commented Nov 8, 2022

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Since current job shuffle data clean up policy is to call remove_job_data for every executor which may not contain any shuffle data of the job. For a large cluster with many executors, many redundant warn logs will be printed in the scheduler side when it detects the executor fail to remove the job shuffle data.

Describe the solution you'd like

It's better for the executor to be silent when no job shuffle data exists.

Describe alternatives you've considered

Additional context

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