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.
Regards,
Guillermo.
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
