I am unsure if this is a network issue on my end, but the login node on Baobab is extremely unresponsive, and slow to navigate around the directories. I have been trying to connect to the cluster and could only login after multiple retries.
Can someone confirm this is the case for them too?
Thanks,
Deb
Hi there,
Debajyoti.Sengupta:
I am unsure if this is a network issue on my end, but the login node on Baobab is extremely unresponsive, and slow to navigate around the directories. I have been trying to connect to the cluster and could only login after multiple retries.
Confirmed, see Current issues on Baobab and Yggdrasil - #45 by Luca.Capello .
FTR, I can easily connect as administrator, which confirms that the node itself does not show problems, but instead the culprit is the access to the HOME/SCRATCH BeeGFS storage.
Unfortunately, resolution time is unknown.
Thx, bye,
Luca
Hi there,
I have just updated the Current issues on Baobab and Yggdrasil - #45 by Luca.Capello , since SCRATCH storage is back to normal “speed”, while HOME is still slow, albeit not deadly slow as one hour ago.
Unfortunately, HOME resolution time is still unknown.
Thx, bye,
Luca
1 Like
Hi there,
Now the HOME storage is back to normal “speed” as well.
Thx, bye,
Luca
Dear HPC Team,
I am facing the same problem as mentioned by @Stephanie.Bron here 3h ago.
Thanks for your efforts,
Best,
Arshia
Login node is still slow. Please look into it.
Thank you.
Hi, please see here for details:
Hi,
the storage on Baobab was unresponsive today 2021-05-02T22:00:00Z (UTC). This impacts the user experience such as using the login node and or the running jobs that are using the storage.
The reason was a user who submitted a job array with every job performing intensive IO operations such as gzip and gunzip of big files. This is clearly something that should be avoided to be done on a compute jobs, specially if this is done dozens of time in parallel.
Best practice:
use the scratch spac…