fix: invalidate ZeRO-3 param coordinator trace in add_hooks #4693
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 does this PR do?
This PR fixes a
IndexError: pop from an empty dequeerror that occurs when usingGKDTrainerwith DeepSpeed ZeRO-3.Problem
When using ZeRO-3, training fails on the second step with:
Root Cause
DeepSpeed registers
fwd_pre_hookseparately fromforward_hookslist. The currentremove_hooks()doesn't removefwd_pre_hook, so during generation,reset_step()is still called on every forward pass, corrupting thePartitionedParameterCoordinator's internal trace state.When
add_hooks()restores hooks without resetting this corrupted state, the subsequent training forward fails.Solution
Call
coordinator._invalidate_trace()inadd_hooks()before re-registering hooks to reset the coordinator to a clean state.Testing
lmbda=0.7,seq_kd=TrueThis fix also benefits other trainers using
unwrap_model_for_generationwith ZeRO-3Before submitting
Pull Request section?
to it if that's the case.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.