Dear Sir,
Thank you for the reply.
I am having total of  7 cores currently. I have created a sample job as shown 
below:-#!/bin/bash#$ -S /bin/bash#$ -l h_rt=01:00:00#$ -R y#$ -j y#$ -e 
/home/chem/test/$JOB_ID.error#$ -o /home/chem/test/$JOB_ID.out#$ -pe orte 4# 
print date and timedatempirun -np $NSLOTS hostname
So i have created 2 sample files with 4 core each and 3 core each and the jobs 
are submitted asqsub sample4.sh; qsub sample4.sh; qsub sample2.sh
But as per my requirement first 4 core job has to be run and the next 4 core 
job has to wait till the first 4 core job gets executed as per FIFO but her 
first 4 core and the 3 core job are running. Kindly help me to get FIFO based 
architecture.
My qconf ssconf output is [locuz@ge ~]$ qconf -ssconfalgorithm                  
       defaultschedule_interval                 0:0:5maxujobs                   
       0queue_sort_method                 loadjob_load_adjustments              
np_load_avg=0.50load_adjustment_decay_time        0:7:30load_formula            
          np_load_avgschedd_job_info                   trueflush_submit_sec     
             0flush_finish_sec                  0params                         
   nonereprioritize_interval             0:0:0halftime                          
168usage_weight_list                 
cpu=1.000000,mem=0.000000,io=0.000000compensation_factor               
5.000000weight_user                       0.250000weight_project                
    0.250000weight_department                 0.250000weight_job                
        0.250000weight_tickets_functional         1weight_tickets_share         
     1share_override_tickets            TRUEshare_functional_shares           
TRUEmax_functional_jobs_to_schedule   200report_pjob_tickets               
TRUEmax_pending_tasks_per_job         50halflife_decay_list               
nonepolicy_hierarchy                  NONEweight_ticket                     
0.010000weight_waiting_time               0.000000weight_deadline               
    3600000.000000weight_urgency                    0.100000weight_priority     
              1.000000max_reservation                   20default_duration      
            8760:00:00

Also i have changed h_rt value ash_rt                  2:00:00
queuename                      qtype resv/used/tot. load_avg arch          
states---------------------------------------------------------------------------------al...@c1.test.server
           BIP   0/4/4          0.00     linux-x64    192 0.60500 sample4.sh 
chem        r     04/04/2016 22:33:50     1    194 0.50500 sample2.sh chem      
  r     04/04/2016 22:33:50     
3---------------------------------------------------------------------------------al...@ge.test.server
           BIP   0/3/3          0.02     linux-x64    192 0.60500 sample4.sh 
chem        r     04/04/2016 22:33:50     3
############################################################################ - 
PENDING JOBS - PENDING JOBS - PENDING JOBS - PENDING JOBS - PENDING 
JOBS############################################################################
    193 0.60500 sample4.sh chem        qw    04/04/2016 22:33:47     4
Username:- chem; queue:- all.q; nodes:- ge.test.server(3 core),c1.test.server(4 
core)Kindly help me to resolve the issue.

Thanks & Regards,A.Narsimha Reddy.

> Subject: Re: [SGE-discuss] Resource Reservation
> From: [email protected]
> Date: Mon, 4 Apr 2016 17:25:09 +0200
> CC: [email protected]
> To: [email protected]
> 
> 
> > Am 02.04.2016 um 19:01 schrieb Narsimha Reddy <[email protected]>:
> > 
> > Dear Team,
> > 
> > Kindly help me out for the implementation of resource reservation in the 
> > Grid Engine.
> > 
> > I want this for the implementation of pure FIFO model to be applied for 
> > grid engine jobs as per the job ids.
> 
> Mostly you need these settings in the scheduler configuration:
> 
> $ qconf -ssconf
> ...
> policy_hierarchy                  NONE
> ...
> max_reservation                   20
> default_duration                  8760:00:00
> 
> and jobs should be submitted with `qsub -R y ...` (could be defined as 
> default in "sge_request"). It's advisable to replace the default runtime with 
> the real expected one. Despite the FIFO scheduling, backfilling could still 
> occur as this would use resources which would idle otherwise and won't 
> influence the FIFO of other jobs.
> 
> -- Reuti
                                          
_______________________________________________
SGE-discuss mailing list
[email protected]
https://arc.liv.ac.uk/mailman/listinfo/sge-discuss

Reply via email to