qalter -w p doesn't shows anything, qstat shows 16 processes and not 60:

    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node2                1 1
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node12               1 2
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node13               1 3
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node11               1 4
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node11               1 5
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node13               1 6
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node12               1 7
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node2                1 8
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node2                1 9
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node12               1 10
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node13               1 11
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node11               1 12
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node11               1 13
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node13               1 14
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node12               1 15
    250 0.50000 OMA        cbuach       r     12/06/2018 11:04:15
main.q@ubuntu-node2                1 16
    250 0.50000 OMA        cbuach       qw    12/06/2018 11:04:02
                          1 17-60:1

El jue., 6 dic. 2018 a las 10:59, Reuti (<re...@staff.uni-marburg.de>)
escribió:

>
> > Am 06.12.2018 um 09:47 schrieb Hay, William <w....@ucl.ac.uk>:
> >
> > On Wed, Dec 05, 2018 at 03:29:23PM -0300, Dimar Jaime Gonz??lez Soto
> wrote:
> >>   the app site is https://omabrowser.org/standalone/ I tried to make a
> >>   parallel environment but it didn't work.
> > The website indicates that an array job should work for this.
> > Has the load average spiked to the point where np_load_avg>=1.75?
>
> Yes, I noticed this too. Hence we need no parallel environement at all, as
> OMA will just start several serial jobs as long as slots are available
> AFAICS.
>
> What does `qstat` show for a running job. There should be a line for each
> executing task while the waiting once are abbreviated in one line.
>
> -- Reuti
>
>
> >
> > I would try running qalter -w p  against the job id to see what it says.
> >
> > William
> >
> >
> >
> >>
> >>> Am 05.12.2018 um 19:10 schrieb Dimar Jaime Gonzalez Soto
> >>     <dimar.gonzalez.s...@gmail.com>:
> >>>
> >>> Hi everyone I'm trying to run OMA standalone on a grid engine setup
> >>     with this line:
> >>>
> >>> qsub -v NR_PROCESSES=60 -b y -j y -t 1-60 -cwd /usr/local/OMA/bin/OMA
> >>>
> >>> it works but only execute 4 processes  per node, there are 4 nodes
> >>     with 16 logical threads.  My main.q configuration is:
> >>>
> >>> qname                 main.q
> >>> hostlist              @allhosts
> >>> seq_no                0
> >>> load_thresholds       np_load_avg=1.75
> >>> suspend_thresholds    NONE
> >>> nsuspend              1
> >>> suspend_interval      00:05:00
> >>> priority              0
> >>> min_cpu_interval      00:05:00
> >>> processors            UNDIFINED
> >>> qtype                 BATCH INTERACTIVE
> >>> ckpt_list             NONE
> >>> pe_list               make
> >>> rerun                 FALSE
> >>> slots                 16
>
>

-- 
Atte.

Dimar González Soto
Ingeniero Civil en Informática
Universidad Austral de Chile
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to