On 17 May 2011 16:09, Reuti <[email protected]> wrote: > Am 17.05.2011 um 15:51 schrieb William Hay: > >> One of our users has submitted an array job of about 5000 tasks. >> >> Some of these tasks are running. Some are not. If I run qstat -s rp >> -u <username> then I see tasks in both states "r" or state "qw". >> Running qstat -s r -u <username> shows the running tasks. However >> running qstat -s p -u <username> does not show the tasks in state qw. > > Correct, there is the option: If this is the "correct behavior" then I have lots of other array jobs that are showing up incorrectly.
> > $ qstat -s p -g d -u <username> > > to list each task on one line on its own. I'm not looking for each task on its own. I do think there should be a single line combining all the queued tasks when I do qstat -s p. The same as qstat -s rp. The same as all the other array jobs that are part queued and part tunning. Essentially I think these two command lines should produce the same output and they don't: (qstat -s r -u '*'|tail -n +3);(qstat -s p -u '*'|tail -n +3 ) qstat -s rp -u '*'|tail -n +3 The line aggregating all the queued tasks only shows up when I use a single qstat with -s rp. Other array jobs do show the queued tasks line when I use qstat -s p The tail -n +3 is just to chop off the headers. > > -- Reuti > > >> These waiting tasks had previously been in an error state caused by a >> problem with our cluster file system but I cleared the error once we >> had fixed >> the problem. Any idea what is going on and whether these tasks will >> eventually run. >> >> William >> _______________________________________________ >> users mailing list >> [email protected] >> https://gridengine.org/mailman/listinfo/users > > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
