I see this with processes that spawn another processes, when you kill the parent the children go free.
On 29 April 2017 at 20:37, Reuti <re...@staff.uni-marburg.de> wrote: > Hi, > > Am 28.04.2017 um 08:57 schrieb Guillermo Marco Puche: > > > I'm expecting a weird behavior when I reschedule any job on my work > cluster. > > > > Suppose I've a job running with id 1000, I reschedule it with the > following command: > > > > qmod -r 1000 > > Pushed rescheduling of job 1000 on host compute-0-3.local > > > > Then if I login into compute-0-3.local and do a top/htop I still see the > process running and consuming resources even if job is now running on > another compute node after rescheduling. I'm experiencing this on jobs > that use a parallel environment like "mpe" and multi-threading. > > Are they still bound to the sge_shepherd or did they jump out of the > process tree? > > -- Reuti > > > > > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
