Fix XGBoost when some workers do not have evals data
#2861
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
qinxuye
added
type: bug
qinxuye
changed the title
evals data
wjsi
pushed a commit
that referenced
this pull request
Mar 24, 2022
qinxuye
added
backported already
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.
What do these changes do?
For now, if
evalsis specified for xgb train, assumedtraindata spans over 3 workers, butevalsdata only exist on 2 workers, the xgb train would become very slow, and cpu usage will be low, that is, at most 1 cpu can be leveraged, this PR fixed this issue.Besides, this PR copied the newest tracker.py from xgboost official repo.
Related issue number
Fixes #2860 .
Check code requirements