[jvm-package] remove the coalesce in barrier mode #7846
Merged
Conversation
This file contains 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
Barrier mode doesn't allow coalesce operation, which should fail all tests of xgboost4j-spark-gpu, but it doesn't. That's because the test file is extremly small which result in only 1 PartitionedFile and finally bypass the checking.
|
@trivialfis, please also port this PR back to 1.6.1 Thx |
This was referenced Apr 27, 2022
Closed
trivialfis
approved these changes
Apr 27, 2022
wbo4958
added a commit
to wbo4958/xgboost
that referenced
this pull request
Apr 28, 2022
trivialfis
pushed a commit
to trivialfis/xgboost
that referenced
this pull request
Apr 29, 2022
trivialfis
added a commit
that referenced
this pull request
Apr 29, 2022
* [jvm-packages] move the dmatrix building into rabit context (#7823) This fixes the QuantileDeviceDMatrix in distributed environment. * [doc] update the jvm tutorial to 1.6.1 [skip ci] (#7834) * [Breaking][jvm-packages] Use barrier execution mode (#7836) With the introduction of the barrier execution mode. we don't need to kill SparkContext when some xgboost tasks failed. Instead, Spark will handle the errors for us. So in this PR, `killSparkContextOnWorkerFailure` parameter is deleted. * [doc] remove the doc about killing SparkContext [skip ci] (#7840) * [jvm-package] remove the coalesce in barrier mode (#7846) * [jvm-packages] Fix model compatibility (#7845) * Ignore all Java exceptions when looking for Linux musl support (#7844) Co-authored-by: Bobby Wang <[email protected]> Co-authored-by: Michael Allman <[email protected]>
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.
Barrier mode doesn't allow coalesce operation, which should fail
all tests of xgboost4j-spark-gpu, but it doesn't. That's because
the test file is extremly small which result in only 1 PartitionedFile
and finally bypass the checking.
This PR makes at least multi-PartitionedFiles for a test file, and
then the existing tests can cover this PR