...
Any number of pilot jobs can be submitted.
Limitations and future plans
- Currently while jobs are running in the JobControlPilot, the memory and cpu time used will always be reported as zero, although when the job completes the CPU time used will be reported normally. This will be fixed soon.
- Currently if the PilotJobDaemon is stopped all information about running jobs will be lost. This will be fixed soon.
- These is no command line for killing running jobs, although jobs can be killed via the workflow engine (perhaps).
- There is currently no support for checkpointing jobs running in the JobControlPilot, although plans are in place to develop such a feature in future and most of the infrastructure required is already in place.