...
- Visibility: Public
- Change Control: Stable
- Details: Introduce new "R" option for qsub which means "remove upon job completion".
- "job completion" means terminated with no errors.
- qsub -R oe job.sh
- The admin can make this behavior as default by using "default_qsub_arguments = -Roe".
- The user has the choice to tell which files has to be deleted. (.e or .o or both)
- This will reflect in qstat -f output as: Remove_Files = oe
Interface 3: Warning messages(MOM) will be generated in the following scenarios.
- Visibility: Public
- Change Control: Stable
- Details:
- The following warning message will be logged if direct write was requested but the path(s) are not usecp-able from the primary execution host.
- "Direct write is requested for job:$job_id but the destination: $final_destination_directory is not usecp-able from $mom_hostname" (DEBUG3)
- Same message will be logged into job's stderr file as well.
The following warning message will be logged if job is rerun (qrerun) to copy the job's standard out/error files back to the Server until job is rescheduled and direct_write is enabled.
"Skipping copy of directly written $which file on rerun of job $jobid" (DEBUG4)
- The following warning will come if the mom comes to a conclusion that the stdout/err files might have written directly and thereby it is not available in the spool area.
- "Skipping directly written/absent spool file$file_path" (DEBUG4)
...
- Visibility: Public
- Change Control: Stable
- Details: A user can change the provided options for a particular job if the job has not started yet.
- Usage of direct_write with qalter:
- qalter -koed $jobid.
- Usage of remove_files with qalter:
- qalter -Roe $jobid.
- If the job has already started running, it will throw the following (already existing) error :
- qalter: Cannot modify attribute while job running Remove_Files $jobid
- Existing behavior of -koe is retained for 'd' option (will throw error if tried to modify a running job).
Interface 5: More lenient way of usage of - k sub-arguments
...