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.

Sign up for GitHub

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

Jump to bottom

[Improvement] (tez): Unregister shuffle data after completing the execution of a DAG. #1165

Closed
3 tasks done
zhuyaogai opened this issue Aug 22, 2023 · 0 comments · Fixed by #1166
Closed
3 tasks done

[Improvement] (tez): Unregister shuffle data after completing the execution of a DAG. #1165

zhuyaogai opened this issue Aug 22, 2023 · 0 comments · Fixed by #1166

Comments

@zhuyaogai
Copy link
Contributor

Code of Conduct

Search before asking

  • I have searched in the issues and found no similar issues.

What would you like to be improved?

Generally, one application will execute multiple DAGs, and there is no correlation between the DAGs. Therefore, after completing the execution of a DAG, you can unregister the relevant shuffle data. Otherwise, when there are many DAGs, an application will occupy a large amount of resources for a long period of time.

How should we improve?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@zhuyaogai zhuyaogai mentioned this issue Aug 22, 2023
Merged
jerqi pushed a commit that referenced this issue Aug 25, 2023
@zhuyaogai
[#1165] improvement(tez): Unregister shuffle data after completing th…
d26da9c 
…e execution of a DAG. (#1166)

### What changes were proposed in this pull request?

Generally, one application will execute multiple DAGs, and there is no correlation between the DAGs. Therefore, after completing the execution of a DAG, you can unregister the relevant shuffle data. Otherwise, when there are many DAGs, an application will occupy a large amount of resources for a long period of time.

### Why are the changes needed?

Fix: #1165

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Existing test cases.
zhuyaogai added a commit to zhuyaogai/incubator-uniffle that referenced this issue Aug 25, 2023
@zhuyaogai
[apache#1165][FOLLOWUP] Fix some spelling mistakes.
c918afa
jerqi pushed a commit that referenced this issue Aug 25, 2023
@zhuyaogai
[#1165][FOLLOWUP] Fix some spelling mistakes. (#1172)
9b725f2 
### What changes were proposed in this pull request?

Fix some spelling mistakes.

### Why are the changes needed?

Fix some spelling mistakes.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

No need.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@zhuyaogai