Dear Riccardo, Sorry for my late answer, I didn't have any runs for a while. It indeed seems to be a memory issue, one of the jobs runs out of memory and the rest of the jobs on that instance terminate as well. I can cancel those jobs with 'gkill'. However, the jobs are not removed from the instance. And although GC3Pie sends new jobs to such an instance, it doesn't make full use of it (e.g. only 3 instead of 4 jobs are running). Except from increasing the memory per core, is there something I can do to at least probably remove the terminated jobs?
Thanks Op vrijdag 5 oktober 2018 09:16:47 UTC+2 schreef Riccardo Murri: > > Dear Hanna, > > sorry for the delay in replying. Based on what you write, my guess as > to what's happening is the following: > > 1. Yours jobs start correctly, possibly multiple jobs per instance > 2. Sometimes a job would fill up the available disk space on a VM -- > in this case part of the output will *not* be generated > 3. For those jobs, GC3Pie will error out while retrieving the output: > the job never moves out of TERMINATING state and attempts to download > its outbox are done again and again. > > Can you please check if this is the case, i.e., if the instances where > the jobs are failing have (near) 100% disk utilization? > > Ciao, > R > -- You received this message because you are subscribed to the Google Groups "gc3pie" group. To unsubscribe from this group and stop receiving emails from it, send an email to gc3pie+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
