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

[CELEBORN-1768][WRITER] Refactoring Shuffle Writer to extract common methods #2985

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

zwangsheng
Copy link
Contributor

What changes were proposed in this pull request?

Refactoring shuffleWriters, extract common methods as BasedShuffleWriter.

Why are the changes needed?

Currently, HashBasedShuffleWriter and SortBasedShuffleWriter have a lot of the same methods, which makes it difficult for us to maintain the code. In many scenarios, we need to update multiple classes at the same time.

Therefore, we need to refactor Shuffle Writer, extract common methods without changing the specific method logic, and simplify the corresponding Shuffle Writer.

Does this PR introduce any user-facing change?

No, we do not change the logic code of apis or others.

How was this patch tested?

UT and local env

@FMX
Copy link
Contributor

FMX commented Dec 9, 2024

Cool. Do test this PR on the cluster, if something is missing, it will cause data correctness problems which are important.

@zwangsheng
Copy link
Contributor Author

Cool. Do test this PR on the cluster, if something is missing, it will cause data correctness problems which are important.

Well, i'll test normal and abnormal cases in yarn cluster laster.

@FMX
Copy link
Contributor

FMX commented Dec 16, 2024

@zwangsheng Hi, How are your tests?

@zwangsheng
Copy link
Contributor Author

@zwangsheng Hi, How are your tests?

Tested on yarn cluster, passing normal Terasort tests, as well as abnormal random task failure tests.

But for the sake of correctness, I still need time to continue testing.

@zwangsheng
Copy link
Contributor Author

Test the normal case(with terasort test) and the abnormal case(RDD with task fail), seems this change is safe.

@FMX plz take a review

@FMX
Copy link
Contributor

FMX commented Jan 3, 2025

Test the normal case(with terasort test) and the abnormal case(RDD with task fail), seems this change is safe.

@FMX plz take a review

OK, please solve the conflicts. The review will be done soon.

Copy link

This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the stale label Jan 27, 2025
Copy link

github-actions bot commented Feb 7, 2025

This issue was closed because it has been staled for 10 days with no activity.

@github-actions github-actions bot closed this Feb 7, 2025
@FMX FMX reopened this Feb 7, 2025
@github-actions github-actions bot removed the stale label Feb 8, 2025
Copy link

This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the stale label Feb 28, 2025
@turboFei turboFei removed the stale label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants