Am 14.08.2014 um 13:19 schrieb Gordon Stewart:

>> You have a project defined here, but in the share tree only the leaf 
>> "default" exists. Can you add a node for the project there too?
> 
> I've now added nodes for the projects, and these nodes do indeed show 
> combined usage values.  If I add users under the project nodes, varying the 
> number of shares allocated to each user has an appropriate effect on the 
> order of queued jobs.  The users under the default node still show no usage.  
> Is this the expected behaviour?
> 
> Perhaps I'm going about things the wrong way.  We require users to submit 
> jobs with projects to simplify our accounting,

Aha, using projects but ignoring them for the scheduling. I must admit that I 
never used such a setup.

There is also the option "-A account_string" to `qsub` where you can supply a 
string which can be accessed later on. It's also recorded in the accounting 
file and handled like a comment regarding scheduling, but can also be used in 
`qacct`.

Do you also want to control who submits jobs to which projects? It would be 
necessary to put it in a JSV then.

-- Reuti


> but would like each user to get a roughly equal share of resources in the 
> long term, regardless of which project they use (i.e. I'd like the share tree 
> to ignore the projects and just work with users).  I sometimes use override 
> tickets to provide a user with a boost when necessary, but otherwise leave 
> the share tree to sort things out.  I'm sure I've managed this previously 
> with a share tree containing just the default node and a list of users 
> underneath, but maybe I'm mistaken.
> 
>> -- Reuti
>> 
>> NB: I suggest to replace the "default_duration INFINITY" below to some high 
>> value. Otherwise jobs may slip in (while you are using backfilling) which 
>> will fit into the remaining runtime of "INFINITY" - and this would always 
>> fit.
> 
> I've modified our configuration following your suggestion.
> 
> Regards,
> 
> 
> Gordon
> 


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

Reply via email to