Am 04.06.2014 um 13:23 schrieb Thomas Achmann (PDF):

> Hi Reuti, thanks for the quick answer.
> 
> yes, the auto_user_fshare is set to 100
> and all users in `qconf -suserl` have fshare 100.

Ok.

Are all these jobs of the same kind, i.e. all serial resp. parallel?

Does the pending job ticket output give any hint, or the various options 
"-urg", "pri" and"-ext" to `qstat` how these values are computed?

-- Reuti


> Thomas Achmann
> 
> 
>> -----Original Message-----
>> From: Reuti [mailto:[email protected]]
>> Sent: Wednesday, June 04, 2014 12:00 PM
>> To: Thomas Achmann (PDF)
>> Cc: [email protected]
>> Subject: Re: [gridengine users] Fair-share problem
>> 
>> Hi,
>> 
>> Am 04.06.2014 um 09:56 schrieb Thomas Achmann (PDF):
>> 
>>> on our SGE-8.1.6 cluster we have implemented fair-share usage w/
>>> functional policy configuration.
>>> As the only limitation we allow to dispatch a maximum of four jobs
>>> concurrently due to license restrictions
>>> of our tool.
>>> 
>>> Fair-share works perfectly fine as long as there are only 4 users
>>> submitting jobs.
>>> 
>>> It looks like this policy fails, as soon as there are more than 4
>> users
>>> submitting jobs.
>>> Any new user's jobs (e.g. 5th user's job) is put into waiting until
>> all
>>> prior submitted jobs of
>>> one of the first four users are completely finished.
>>> 
>>> Any help to make fair-share working for more than 4 users is greatly
>>> appreciated.
>>> 
>>> I'm attaching scheduler config settings. Please let me know, if you
>> need
>>> more details.
>> 
>> Did you also set "auto_user_fshare             100" in SGE's
>> configuration?
>> 
>> All users with running jobs should get an entry in `qconf -suserl`and
>> have the same set for "fshare". This will be set when the user is
>> automatically created, but not automatically updated when the value in
>> SGE's configuration is changed.
>> 
>> -- Reuti
>> 
>> 
>>> Kind regards,
>>> 
>>> Thomas Achmann
>>> 
>>> qconf -ssconf
>>> algorithm                         default
>>> schedule_interval                 0:0:10
>>> maxujobs                          0
>>> queue_sort_method                 load
>>> job_load_adjustments              NONE
>>> load_adjustment_decay_time        0:0:0
>>> load_formula                      -slots
>>> schedd_job_info                   true
>>> flush_submit_sec                  0
>>> flush_finish_sec                  0
>>> params                            none
>>> reprioritize_interval             0:0:0
>>> halftime                          168
>>> usage_weight_list
>> cpu=1.000000,mem=0.000000,io=0.000000
>>> compensation_factor               5.000000
>>> weight_user                       1.000000
>>> weight_project                    0.000000
>>> weight_department                 0.000000
>>> weight_job                        0.000000
>>> weight_tickets_functional         1000000
>>> weight_tickets_share              0
>>> share_override_tickets            TRUE
>>> share_functional_shares           TRUE
>>> max_functional_jobs_to_schedule   2000
>>> report_pjob_tickets               TRUE
>>> max_pending_tasks_per_job         50
>>> halflife_decay_list               none
>>> policy_hierarchy                  OFS
>>> weight_ticket                     10.000000
>>> weight_waiting_time               0.000000
>>> weight_deadline                   3600000.000000
>>> weight_urgency                    0.000000
>>> weight_priority                   0.000000
>>> max_reservation                   0
>>> default_duration                  INFINITY
>>> 
>>> --
>>> *This message may contain confidential and privileged information. If
>> it
>>> has been sent to you in error, please reply to advise the sender of
>> the
>>> error and then immediately permanently delete it and all attachments
>> to it
>>> from your systems. If you are not the intended recipient, do not
>> read,
>>> copy, disclose or otherwise use this message or any attachments to
>> it. The
>>> sender disclaims any liability for such unauthorized use. PLEASE NOTE
>> that
>>> all incoming e-mails sent to PDF e-mail accounts will be archived and
>> may
>>> be scanned by us and/or by external service providers to detect and
>> prevent
>>> threats to our systems, investigate illegal or inappropriate
>> behavior,
>>> and/or eliminate unsolicited promotional e-mails ("spam"). If you
>> have any
>>> concerns about this process, please contact us at *
>>> *[email protected]* <[email protected]>*.*
>>> 
>>> _______________________________________________
>>> users mailing list
>>> [email protected]
>>> https://gridengine.org/mailman/listinfo/users
>>> 
> 
> -- 
> *This message may contain confidential and privileged information. If it 
> has been sent to you in error, please reply to advise the sender of the 
> error and then immediately permanently delete it and all attachments to it 
> from your systems. If you are not the intended recipient, do not read, 
> copy, disclose or otherwise use this message or any attachments to it. The 
> sender disclaims any liability for such unauthorized use. PLEASE NOTE that 
> all incoming e-mails sent to PDF e-mail accounts will be archived and may 
> be scanned by us and/or by external service providers to detect and prevent 
> threats to our systems, investigate illegal or inappropriate behavior, 
> and/or eliminate unsolicited promotional e-mails (“spam”). If you have any 
> concerns about this process, please contact us at *
> *[email protected]* <[email protected]>*.*
> 


_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to