Service Alerts
LSF Queue Changes
We have been working on improving our LSF queuing policy. The goal is to maximize the use of the available CPU power and at the same time, minimize the waiting (pending) times on the queues, thus speeding up the overall work-flow for our users. After careful consideration we have implemented the following changes which have been well received from users:
- ** The short_serial and normal_serial queues have been modified such that jobs from these queues are allowed to run on all “owned” compute nodes when there are idle cpus. When higher priority jobs are submitted to “owned” nodes, jobs from the short_serial or normal_serial queues will be killed and re-queued as needed so the higher priority jobs can run. This policy allows jobs from the short_serial and normal_serial queues to run on many more cores, while satisfying the requirement that higher priority jobs don’t contend with resources taken by short_serial and normal_serial jobs. Consequently, you may receive email alerts from LSF that some of your jobs have been automatically re-queued.
- ** The long_serial queue had an additional 278 cores added. A total of 344 cores are available to this queue now. This should improve job throughput for this queue.
Universal Desktop (UD) systems and mapping RCFS1, 2, 3 shares
Description of issue:
Some users who just received a UD computer were able to see their mapped network drives, but upon attempting to open files, they received “Access Denied” or messages indicating improper credentials were supplied.
Resolution:
To correct this issue, the user simply needs to disconnect from their mapped folders using the following command:
net use * /delete
(If prompted, confirm that all folders are being disconnected.)
Without using this command first, you will likely see an error stating that the folder is already mapped using other credentials. (in some cases, that mapping may have been made using the a different account)
Re-Mapping users RC storage folders.
Once all connections are cleared, remapping the drive with your individual users credentials can be performed. When re-mapping your drives, it is important to use the option to “Specify Alternate Credentials,” which will cause a prompt to appear and allow you to supply your RC credentials instead of your FAS_DOMAIN username which would otherwise automatically be supplied by your desktop computer.
If you require further assistance, please contact the RC at rchelp@fas.harvard.edu.
Some users who just received a UD computer were able to see their mapped network drives, but upon attempting to open files, they received “Access Denied” or messages indicating improper credentials were supplied.
Resolution:
To correct this issue, the user simply needs to disconnect from their mapped folders using the following command:
net use * /delete
(If prompted, confirm that all folders are being disconnected.)
Without using this command first, you will likely see an error stating that the folder is already mapped using other credentials. (in some cases, that mapping may have been made using the a different account)
Re-Mapping users RC storage folders.
Once all connections are cleared, remapping the drive with your individual users credentials can be performed. When re-mapping your drives, it is important to use the option to “Specify Alternate Credentials,” which will cause a prompt to appear and allow you to supply your RC credentials instead of your FAS_DOMAIN username which would otherwise automatically be supplied by your desktop computer.
If you require further assistance, please contact the RC at rchelp@fas.harvard.edu.