Skip to content

Fix multivalidation - #3388

Merged
asolergi-nv merged 10 commits into
NVIDIA:mainfrom
RPrenger:fix_multivalidation
Apr 25, 2026
Merged

Fix multivalidation#3388
asolergi-nv merged 10 commits into
NVIDIA:mainfrom
RPrenger:fix_multivalidation

Conversation

@RPrenger

Copy link
Copy Markdown
Contributor

What does this PR do ?

This fixes a bug where using multiple validation sets hangs training if the validation sets are small compared to data parallel size.

Contribution process

flowchart LR
    A[Pre-checks] --> B[PR Tests]
    subgraph Code Review/Approval
        C1[Expert Review] --> C2[Final Review]
    end
    B --> C1
    C2 --> D[Merge]
Loading

Pre-checks

  • I want this PR in a versioned release and have added the appropriate Milestone (e.g., Core 0.8)
  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

The following process is enforced via the CODEOWNERS file for changes into megatron/core. For changes outside of megatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.

For MRs into `main` branch

Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

(Step 1): Add PR label Expert Review

(Step 2): Collect the expert reviewers reviews

  1. Attach the Expert Review label when your PR is ready for review.
  2. GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.

⚠️ Only proceed to the next step once all reviewers have approved, merge-conflict are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

(Step 3): Final Review

  1. Add Final Review label
  2. GitHub auto-assigns final reviewers based on your changes. They will get notified and pick up your PR soon.

(Optional Step 4): Cherry-pick into release branch

If this PR also needs to be merged into core_r* release branches, after this PR has been merged, select Cherry-pick to open a new PR into the release branch.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either eharper@nvidia.com or zijiey@nvidia.com.

Merging your PR

Any member of core-adlr and core-nemo will be able to merge your PR.

@copy-pr-bot

copy-pr-bot Bot commented Feb 12, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@ko3n1g
ko3n1g requested a review from a team February 12, 2026 17:46
@RPrenger RPrenger added the Expert Review [deprecated] Apply this label to indicate that your PR is ready for expert review. label Feb 23, 2026
@Phlip79

Phlip79 commented Mar 3, 2026

Copy link
Copy Markdown
Member

/ok to test 2c4221b

@svcnvidia-nemo-ci svcnvidia-nemo-ci added this to the Core 0.16 milestone Mar 3, 2026
@Phlip79
Phlip79 requested a review from a team March 3, 2026 17:55
if split == Split.valid and args.full_validation:
batch_sampler = MegatronPretrainingSampler(
# Use specialized sampler for full validation that handles small datasets
batch_sampler = MegatronFullValidationSampler(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we only use MegatronFullValidationSampler when required? (When using small datasets & full_validation)

Otherwise keep MegatronPretrainingSampler

Note we can access len(dataset) & DP size

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we need it whenever we're doing full_validation. The wording of the comment is a little confusing though. Should I change it?

@RPrenger
RPrenger requested review from a team as code owners April 16, 2026 23:26
@Phlip79 Phlip79 removed the Expert Review [deprecated] Apply this label to indicate that your PR is ready for expert review. label Apr 16, 2026
@Phlip79
Phlip79 requested a review from asolergi-nv April 16, 2026 23:29
@RPrenger

Copy link
Copy Markdown
Contributor Author

/ok to test 66028ab

…erators

  The previous change ran the cross-DP all-reduce of eval_iters
  unconditionally and dropped the per-dataloader _get_iterator calls,
  which (1) failed with `TypeError: object of type 'list_iterator' has
  no len()` when dataloader_type="external" and (2) left
  valid_data_iterators set to None for non-full-validation runs.

  Gate the all-reduce on args.full_validation and restore the
  _get_iterator calls for both multiple_validation_sets and single-set
  paths, using "cyclic" iteration only under full_validation so short
  DP ranks loop up to the MAX-reduced eval_iters.
@RPrenger

Copy link
Copy Markdown
Contributor Author

/ok to test 0fcfa93

@RPrenger

Copy link
Copy Markdown
Contributor Author

/ok to test b4855d3

@RPrenger

Copy link
Copy Markdown
Contributor Author

/ok to test 72d6cf1

@svcnvidia-nemo-ci svcnvidia-nemo-ci added the Approved All necessary approvals have been made label Apr 24, 2026
@asolergi-nv
asolergi-nv enabled auto-merge April 24, 2026 20:29
@asolergi-nv
asolergi-nv added this pull request to the merge queue Apr 24, 2026
@svcnvidia-nemo-ci

Copy link
Copy Markdown
Contributor

🔄 Merge queue validation started!

You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/24910443901

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 24, 2026
@asolergi-nv
asolergi-nv added this pull request to the merge queue Apr 25, 2026
@svcnvidia-nemo-ci

Copy link
Copy Markdown
Contributor

🔄 Merge queue validation started!

You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/24938930211

Merged via the queue into NVIDIA:main with commit 241a5ca Apr 25, 2026
69 of 74 checks passed
yangbofun pushed a commit to xlm-research/Megatron-LM that referenced this pull request May 22, 2026
Signed-off-by: rprenger <rprenger@nvidia.com>
yhgalaxy pushed a commit to yhgalaxy/Megatron-LM that referenced this pull request Jun 17, 2026
Signed-off-by: rprenger <rprenger@nvidia.com>
Signed-off-by: yhgalaxy <yhgalaxy@outlook.com>
jon-barker pushed a commit to jon-barker/Megatron-LM that referenced this pull request Jul 10, 2026
Signed-off-by: rprenger <rprenger@nvidia.com>
Signed-off-by: Jon Barker <jbarker@aws-cmh-slurm-1-vscode-02.cm.cluster>
terminator123 pushed a commit to 021ai/Megatron-LM that referenced this pull request Aug 3, 2026
Signed-off-by: rprenger <rprenger@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved All necessary approvals have been made

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants