Skip Dataproc shuffle manager auto-configuration - #15420
Merged
sameerz merged 2 commits intoJul 30, 2026
Merged
Conversation
Dataproc uses a Spark-specific shuffle ABI that is incompatible with the RAPIDS shuffle manager selected automatically for Spark 4. Keep spark.shuffle.manager unset when spark.dataproc.engine is present, while preserving explicitly configured managers. Fixes NVIDIA#15418. Signed-off-by: Chong Gao <chongg@nvidia.com>
res-life
force-pushed
the
fix/dataproc-auto-shuffle-manager
branch
from
July 29, 2026 09:03
0beff0e to
66cfe35
Compare
Collaborator
Author
|
build |
Contributor
Greptile SummaryThe PR prevents automatic RAPIDS Shuffle Manager selection on Dataproc runtimes while preserving explicit shuffle-manager settings.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Driver plugin initialization] --> B{spark.dataproc.engine present?}
B -->|Yes| C[Leave shuffle manager unchanged]
B -->|No| D{Shuffle manager explicitly configured?}
D -->|Yes| C
D -->|No| E[Apply supported RAPIDS shuffle auto-configuration]
Reviews (2): Last reviewed commit: "Clarify Dataproc shuffle auto-configurat..." | Re-trigger Greptile |
wjxiz1992
reviewed
Jul 30, 2026
wjxiz1992
left a comment
Collaborator
There was a problem hiding this comment.
One non-blocking documentation precision nit.
Signed-off-by: Chong Gao <chongg@nvidia.com>
Collaborator
Author
|
build |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #15418.
Description
#15285 changed behavior, now auto set shuffle manager. It impacts the behavior of Dataporc pipeline.
Dataproc's Spark 4.0.1 runtime uses a shuffle resolver ABI that differs from the Apache Spark ABI expected by the RAPIDS Shuffle Manager. After shuffle manager auto-configuration was enabled for Spark 4, workloads that did not explicitly configure
spark.shuffle.managerbegan selecting the RAPIDS implementation and failed during shuffle output commit withNoSuchMethodError.Skip RAPIDS Shuffle Manager auto-configuration when
spark.dataproc.engineis present. This restores the previous behavior on Dataproc by leavingspark.shuffle.managerunset, while continuing to preserve any explicitly configured shuffle manager. The configuration documentation is updated to describe this exception.Added
RapidsPluginUtilsSuitecoverage for the Dataproc guard.Validation:
RapidsPluginUtilsSuitepassed (6 tests).Checklists
Documentation
Testing
(Please provide the names of the existing tests in the PR description.)
Performance