Limit reading/mounting from shared filesystem JobStore #5047
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.
This fixes #4673 by adding a
--symlinkJobStoreReads
option.If you set
--symlinkJobStoreReads=False
, we won't create symlinks pointing into a FileJobStore when jobs go to read from it. We will instead make copies or hardlinks (within a filesystem). So if you have a workload that does more I/O on a file mounted into a container than a single full copy would do, you can use this to make a copy happen instead of having everyone mount straight from the shared filesystem.If you have caching enabled, you can make the cache actually cache a copy per node instead of symlinking all the way through just because it can.
Changelog Entry
To be copied to the draft changelog by merger:
--symlinkJobStoreReads=False
option lets you force local-node copies (possibly in the cache) even when reading directly from a FileJobStore is possible, potentially reducing shared filesystem IO.Reviewer Checklist
issues/XXXX-fix-the-thing
in the Toil repo, or from an external repo.camelCase
that want to be insnake_case
.docs/running/{cliOptions,cwl,wdl}.rst
Merger Checklist