Fix subgroup optimizer metadata inconsistency #7820
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.
Description
This PR addresses Issue #7819.
When using ZeRO Stage-3 + CPU offloaded optimizer (CPUAdam) with 2+ subgroups,
ds_adam_stepcan be invoked multiple times within a single global optimizer step. Before this fix, the internal bias-correction-related state (e.g.,_betta2_t→_bias_correction2) could become inconsistent across subgroup invocations within the same step, leading to subgroup-wise optimizer state divergence.Solution
Make
IncrementStep()step-consistent under repeated calls in the same global step.Change
Update
IncrementStep()to only advance or recompute state whenstep != _step, preventing subgroup-to-subgroup drift inside a single step.