Hello all,
'something' is causing our iRODS (4.2.10) icat-servers to run out of memory:
[wo mei 25 14:06:18 2022] Out of memory: Kill process 32098 (irodsServer) score 175 or sacrifice child
[wo mei 25 14:06:18 2022] Killed process 32098 (irodsServer), UID 998, total-vm:3841276kB, anon-rss:3066772kB, file-rss:224kB, shmem-rss:156kB
We think it is the Cyberduck client sending large files through the icat server instead of directly to the resc-servers. Has anyone else seen this behaviour?
CyberDuck's parallel transfer mode is enabled by default, but appears to connect to the icat servers instead of any of the resource servers, likely causing the problem.
Of course it could be something completely else so, any tips/tricks on how to tackle out of memory issues would also be nice.
Our icat systems have 16 GB of memory and 2 GB swap. Perhaps that is a bit too small. What is considered 'normal'?
--
Vriendelijke groet,
Ger Strikwerda
senior expert multidisciplinary enabler
simple solution architect
Rijksuniversiteit Groningen
CIT/RDMS/HPC
Smitsborg
Nettelbosje 1
9747 AJ Groningen
Tel. 050 363 9276
"God is hard, God is fair
some men he gave brains, others he gave hair"