This will write potion of the definition to disk and restore on re-queue/begin
This helps in coping with extra large suites.
Archives suite or family nodes *IF* they have child nodes(otherwise does nothing).
Saves the suite/family nodes to disk, and then removes the child nodes from the definition
This saves memory in the server, when dealing with huge definitions that are not needed.
It improves time taken to checkpoint and reduces network bandwidth
If the node is re-queued or begun, the child nodes are automatically restored
Use ecflow_client --restore to reload the archived nodes manually
Care must be taken if you have trigger reference to the archived nodes
The nodes are saved to ECF_HOME/<host>.<port>.ECF_NAME.check, where '/' has been replaced with ':' in ECF_NAME
- ecflow_client --archive=/s1 # archive suite s1
- ecflow_client --archive=/s1/f1 /s2 # archive family /s1/f1 and suite /s2
- ecflow_client --archive=force /s1 /s2 # archive suites /s1,/s2 even if they have active tasks
Archived nodes can be restored manually with a user command or automatically via autorestore attribute in the definition.
Restore will fail if:
- Node has not been archived
- Node has children, i.e as a part of replace
- If the file ECF_HOME/ECF_NAME.check does not exist
- ecflow_client --restore=/s1/f1 # restore family /s1/f1
- ecflow_client --restore=/s1 /s2 # restore suites /s1 and /s2
Suite and Family nodes can also be restored with attribute autorestore.
Whenever a node completes we check if it has a autorestore attribute.
If it does, we then try to restore from disk the referenced suite/family node.