Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dws: saving nnfdatamovements #216

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

jameshcorbett
Copy link
Member

@jameshcorbett jameshcorbett commented Sep 19, 2024

Fixes #212
Fixes #180

Problem: sometimes it may be useful to save a fixed number of
nnfdatamovements for each job to the KVS.

Add a command-line option to determine how many (max) to save.
Problem: `move_workflow_to_teardown` would be simpler if it were an
instance method of the `WorkflowInfo` class.

Make it an instance method.
Problem: it may be useful for debugging to have access to some
number of nnfdatamovement resources. The KVS is a natural place
to store the info, since it is available to general users.

Save some number of the resources to a jobs' KVS.
Problem: there are no checks to ensure nnfdatamovements are saved
to jobs' KVS.

Add some checks and make some changes to reduce the likelihood of
timeouts on some tests that create and destroy large filesystems.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Save a configurable number of nnfdatamovement resources to the KVS Saving some workflow info to job KVS
1 participant