Skip to content

fully remove zarr support#2944

Merged
dimapihtar merged 4 commits into
NVIDIA:mainfrom
dimapihtar:remove_zarr
Jan 16, 2026
Merged

fully remove zarr support#2944
dimapihtar merged 4 commits into
NVIDIA:mainfrom
dimapihtar:remove_zarr

Conversation

@dimapihtar

@dimapihtar dimapihtar commented Jan 14, 2026

Copy link
Copy Markdown
Contributor

What does this PR do ?

Fully removes checkpointing zarr strategy support. Zarr format is already deprecated and no longer supported so we want to clean up our dist checkpointing codepaths by removal zarr codepaths.

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact the @mcore-oncall.

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.

Signed-off-by: dimapihtar <dpihtar@gmail.com>
@copy-pr-bot

copy-pr-bot Bot commented Jan 14, 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.

@dimapihtar dimapihtar marked this pull request as ready for review January 14, 2026 14:36
@dimapihtar dimapihtar requested review from a team as code owners January 14, 2026 14:36
@ko3n1g ko3n1g requested a review from a team January 14, 2026 14:36
@dimapihtar

Copy link
Copy Markdown
Contributor Author

/ok to test 3ba3801

@dimapihtar dimapihtar requested a review from yaoyu-33 January 14, 2026 16:00

@Phlip79 Phlip79 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you explain why we're removing zarr support in the description please?

@Phlip79 Phlip79 added Final Review PR is in the "final review" stage complexity: low labels Jan 14, 2026
@dimapihtar

Copy link
Copy Markdown
Contributor Author

/ok to test 50b1947

@dimapihtar

Copy link
Copy Markdown
Contributor Author

/ok to test fc399ea

@dimapihtar

Copy link
Copy Markdown
Contributor Author

/ok to test ad5c259

@dimapihtar dimapihtar added this pull request to the merge queue Jan 16, 2026
Merged via the queue into NVIDIA:main with commit faa6037 Jan 16, 2026
42 of 47 checks passed
@dimapihtar dimapihtar deleted the remove_zarr branch January 16, 2026 11:53
daiyaanarfeen pushed a commit to daiyaanarfeen/Megatron-LM that referenced this pull request Feb 23, 2026
Signed-off-by: dimapihtar <dpihtar@gmail.com>
yangbofun pushed a commit to xlm-research/Megatron-LM that referenced this pull request May 22, 2026
Signed-off-by: dimapihtar <dpihtar@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

complexity: low Final Review PR is in the "final review" stage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants