Page History

The new Juno juno cluster is now available to the test users only . Please, create a request if for testing. Please request "Access another cluster" from http://hpc.mskcc.org/compute-accounts/account-change-request/ if you want to participate in the test. It is juno currently composed of has 216 CPUs. The login node name is juno. It's a CentOS 7.3 host. The latest CentOS 7 .3 Linux operating system is on nodes jx01-jx10  and the Centos 6 .9 Linux operating system is on node ju14 ju14. All cluster nodes have access to the solisi Isilon solisi file systemsystems. The CentOS 7 .3 nodes also have access to the GPFS storage named junoto /juno GPFS storage.

Differences in LSF configuration between Juno and Luna

1. We reserve ~12GB of RAM per host for the operating system and GPFS on Juno CentOS 7 hosts.
2. On each jx## node (CentOS 7, GPFS installed), 240GB of RAM is available for LSF jobs.
3. On each ju## node (CentOS 6, no GPFS), 250GB of RAM is available for LSF jobs.
4. When specifying RAM for LSF jobs, specify GB of RAM per slot/task on Juno, or per job on Lunaluna.
5. All jobs must have -W (maximum Walltime) specified on Junojuno. Please do not use -We on Junojuno.
6. To check jobs which are DONE or status EXIT, use "bhist -l JobID" or "bhist -n 0 -l JobID". bacct is also available. "bjobs -l JobID" only shows RUNNING and PEND jobs.
7. There is no /swap on CentOS 7 nodes. Memory usage is enforced by cgroups , so job jobs never use / swap. A job will be terminated if memory usage exceeds its LSF specification.
8. There is no iounits resource on Junojuno.

Queues

The Juno cluster uses LSF (Load Sharing Facility) 10.1  FP6 from IBM to schedule jobs. The default LSF queue, ‘general’, includes all Juno compute nodes.

...