Hi, I can also see that behaviour under SGE long running jobs, like blast+. Screenshot attached. Cheers, Bjoern
On Tue, Feb 18, 2014 at 2:20 PM, Federico Zambelli <federico.zambelli@unimi.it> wrote:
Hi,
something strange happens with Cufflinks in our Galaxy server. When a user deletes a running Cufflinks job in fact the associated Cufflinks process(es) are not terminated. Apart from unneccessary CPU usage, this prevents other jobs from starting if the max jobs limit has been already reached by the user.
This happens only with Cufflinks, Cuffcompare for comparison behaves just fine.
Best, F. What cluster system are you using? Can you try a few other long running tools for comparison?
I've been meaning to double check if this still happens, but I had seen this for BLAST+ jobs under SGE (noticeable again when large zombie jobs are blocking the queue).
Peter ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
