Closed RvV1979 closed 1 year ago
Hi @RvV1979,
ah yes, this indeed seems to be a Java OOM, which won't be showing up in the slurm logs. This has been addressed in grenepipe v0.12.1, where I added support for extra Java options, for exactly that type of error. The option is called MarkDuplicates-java-opts
, see here. The documentation there also states how to specify memory.
So, simply get the new version of grenepipe, set the memory as needed, and then hopefully that works ;-)
Cheers and so long Lucas
I can confirm that the issue is resolved by using the latest version and specifying MarkDuplicates-java-opts: "-Xmx40g"
Thanks for the prompt support!
Hi Lucas,
I am running grenepipe v0.12.0 via slurm and run into an error with rule
mark_duplicates
on some of my samples. Based on the picard logfile, it looks like the deduplication process finishes, but also throws an Out of Memory error. See tail of logfile, below:I tried increasing the allocated memory via profile/slurm.yaml but this did not help. In any case, the slurm job did not throw a memory error so I am guessing the issue lies with the java process not having not enough allocated memory. However, i could not find a way to increase allocated memory for java.
Do you have an idea what may be going wrong and how I might solve this issue?
Thanks