Increase vmem limit for markdup
The re-analysis for an old sample (10303873) failed because the markdup
job is killed by the cluster for using too much vmem.
qacct -j 3498299 ============================================================== qname all.q
hostname chimerashark.researchlumc.nl group Domain
owner sa_capturelumc
project KG
department defaultdepartment
jobname hutspot.184
jobnumber 3498299
taskid undefined account sge
priority 0
qsub_time Mon Nov 11 18:01:10 2019 start_time Mon Nov 11 18:01:41 2019 end_time Mon Nov 11 18:01:44 2019 granted_pe BWA
slots 1
failed 100 : assumedly after job exit_status 137
ru_wallclock 3
ru_utime 0.000
ru_stime 0.010
ru_maxrss 1528
ru_ixrss 0
ru_ismrss 0
ru_idrss 0
ru_isrss 0
ru_minflt 714
ru_majflt 0
ru_nswap 0
ru_inblock 8
ru_oublock 16
ru_msgsnd 0
ru_msgrcv 0
ru_nsignals 0
ru_nvcsw 35
ru_nivcsw 4
cpu 2.450
mem 8.289
io 0.021
iow 0.000
maxvmem 10.167G arid undefined
The solution is to increase the amount of vmem this job can use.