Move NERSC job/refdata transfers from SFAPI tasks to Perlmutter Slurm jobs - #744
Merged
Conversation
jobs SFAPI async tasks are canceled ~10 minutes after completion, which was becoming a reliability problem for tracking longer-running transfers. Downloads/ uploads for jobs and refdata now run as `xfer` QOS Slurm jobs on Perlmutter instead, submitted and polled through the regular Slurm APIs. Refdata's final destination is a DTN-only-writable filesystem, so refdata downloads still need a DTN hop: the Perlmutter job stages files locally then rsyncs them to the DTN over the existing sshproxy key and writes the JAWS completion file remotely. Regular job I/O has no such constraint and stays entirely on Perlmutter. Renames NERSC *_task_id fields/log fields/update_state functions to *_job_id, keeping the old fields as deprecated (nullable) for records written before the migration. Removes the now-unused jaws_staging_dir_dtn config/path. Also tracks per-file sizes in the checksum manifest so Slurm wall-time limits can be computed from total transfer size.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #744 +/- ##
=======================================
Coverage 64.38% 64.39%
=======================================
Files 68 68
Lines 6953 6971 +18
=======================================
+ Hits 4477 4489 +12
- Misses 2476 2482 +6 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
SFAPI async tasks are canceled ~10 minutes after completion, which was becoming a
reliability problem for tracking longer-running transfers. Downloads/ uploads for jobs and refdata now run as
xferQOS Slurm jobs on Perlmutter instead, submitted and polled through the regular Slurm APIs.Refdata's final destination is a DTN-only-writable filesystem, so refdata downloads still need a DTN hop: the Perlmutter job stages files locally then rsyncs them to the DTN over the existing sshproxy key and writes the JAWS completion file remotely. Regular job I/O has no such constraint and stays entirely on Perlmutter.
Renames NERSC *_task_id fields/log fields/update_state functions to *_job_id, keeping the old fields as deprecated (nullable) for records written before the migration. Removes the now-unused jaws_staging_dir_dtn config/path. Also tracks per-file sizes in the checksum manifest so Slurm wall-time limits can be computed from total transfer size.