CMS Tier-3 News Item
Introduction of new walltime limits for all.q, long.q. New interactive debugging queue
Summary
On Nov 28, Based on the agreed policies, we will introduce a limit of 10h for jobs on the all.q and 96h on the long.q. The new interactive debugging queue is now also accessible for users.
Details
New walltime limits for all.q and long.q
The ALL.Q will be our queue for MEDIUM LENGTH jobs, and it will have a runtime limit of 10h. All of your jobs that run longer than this you should from now on submit to the new LONG.Q that will have a maximal runtime of 96h.
For the moment both all.q and long.q have the exact same time limits as the original all.q had (48h), so that you can start migrating to the new submission rules. But by Nov 28 we will enforce the new configuration and all jobs longer than 10h on the all.q will run into the new limit.
You can get the details on the
policies page
Interactive queue for debugging: debug.q
There is now an interactive queue that you may use for launching an interactive shell on a worker node.
Please do not abuse this facility since it has the potential for interfering with other users' jobs. The queue has a limited runtime of 20min walltime (10 min CPU time), so after that time you will be logged off. There is only one such slot available per node at any time.
You can get all the details on the following page:
How to interactively debug jobs
DerekFeichtinger 23. 11. 2011