Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

SGE configuration resulting in memory blocked jobs in H-series nodes

Abierto
#21 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@mvrequa ya está trabajando en esto.

Desde el 3/8/2021.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Cyclecloud version: 8.1.0-1275
OS Image: HPC:CentOS8.1
Problem: Issues with Infiniband connectivity

I was running a small cluster in cyclecloud 7 and recently I updated to cyclecloud 8, the cluster has several node arrays, some non H-series and other H-series for MPI heavy calculations. I noticed that there seems to be a different behaviour in the Infiniband connectivity between 7 and 8. I have tracked part of the problem to the SGE configuration.

The SGE configuration provided in cyclecloud 8.1.0-1275 with the HPC:CentOS8.1 has the variable execd_params set to none. This can result in problems when trying to execute MPI jobs in H-series nodes with Infiniband.
The jobs would fail reporting that the the process cannot allocate the necessary memory, this issue can be manually fixed by setting execd_params H_MEMORYLOCKED=unlimited.
I have tested this using several MPI heavy programs such as VASP and QE , which were running in non H-series nodes without problem, but when trying to run in H-series would consistently fail. After the change of execd_params the programs would run.

However, something I noticed from updating to cyclecloud8 from cyclecloud7 is that running MPI jobs in non H-series jobs using inter node communication seems to no longer be possible.

Lenguaje dominante
Python
Estrellas
7
Forks
18
Merge medio
1 d 5 h
PR fusionados (30 d)
5

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/cyclecloud-gridengine

Todos los issues de Azure/cyclecloud-gridengine

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.