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-1853] Remove idle executors when DRA enable and using Celeborn #3088

Closed
wants to merge 2 commits into from

Conversation

zaynt4606
Copy link
Contributor

@zaynt4606 zaynt4606 commented Feb 6, 2025

What changes were proposed in this pull request?

Remove idle executors when spark.dynamicAllocation.enabled is true and using Celeborn

Why are the changes needed?

When using Celeborn as remote shuffle service, the idle executors can be removed although hasActiveShuffle is true in DRA condition.

Does this PR introduce any user-facing change?

Spark patch change.

How was this patch tested?

Cluster testing.

@photogamerun
Copy link

what's DRA can you please give detail name?

@zaynt4606
Copy link
Contributor Author

what's DRA can you please give detail name?

spark.dynamicAllocation.enabled

// from a Standalone cluster, where the shuffle service lives in the Worker.)
- val fileLost = !sc.shuffleDriverComponents.supportsReliableStorage() &&
+ val fileLost = !Utils.isCelebornEnabled(sc.getConf) &&
+ !sc.shuffleDriverComponents.supportsReliableStorage() &&
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why !sc.shuffleDriverComponents.supportsReliableStorage() is not sufficent here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the doc:

# Support Spark Dynamic Resource Allocation
# Required Spark version >= 3.5.0
spark.shuffle.sort.io.plugin.class org.apache.spark.shuffle.celeborn.CelebornShuffleDataIO

@zaynt4606 zaynt4606 marked this pull request as draft February 8, 2025 08:44
Copy link

github-actions bot commented Mar 5, 2025

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 Mar 5, 2025
@zaynt4606 zaynt4606 closed this Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants