On 04/17/2014 02:24 PM, Jeff Templon wrote:
> Hi Goncalo,
>
> On Apr 17, 2014, at 13:12 , Gonçalo Borges<[log in to unmask]> wrote:
>
>
>> Hi Jeff...
>>
>> Not sure if I really understood your point.
>>
>> If the same user is always mapped to the same unix account, independently of the CE, the batch system should enforce the limit based on that unix account information. In this sense, CREAM should be agnostic to this process. If that limit is really enforced, CREAM should receive an error from BLAH at qsub time.
>>
>> Did I missed something?
>>
>>
> yes, i think so, or possibly I have a inflated sense of the clarity of my own explanations, one or the other ;-) Let me try again:
>
>
>>> in Torque. Now comes the problem : CREAM appends "@machine" to the user name, and even though torque sees that it's the same user
>>>
>>> euser = biome053
>>>
>>> it seems to use the field "Job_Owner" for determining whether max_user_queuable has been reached:
>>>
>>> Job_Owner = [log in to unmask]
>>>
> indeed somehow torque knows that it’s all the same unix account (euser) and this is also what is used for enforcing *Maui* throttling policies like MAXPROC on the same set of jobs. However, as far as I can tell, what counts to *torque* for max_user_queuable is not “euser” but “Job_Owner”. Since jobs coming from different CREAM hosts have different Job_Owners even though they have the same euser, Torque allows up to max_user_queuable from *each separate CREAM machine*.
>
> I agree with you that torque SHOULD only look at euser, but as far as I can tell without looking at the source code, it is not doing what it SHOULD. The documentation of torque is poor enough that it is difficult to tell whether this is intended behavior, or a bug — it just talks about “user” and not whether this means “euser” or “job owner”.
>
Hi Jeff,
I don't think that CREAM appends anything to job_owner, probably it's
done inside qsub.
Do you see different behaviour in jobs submitted with qsub by hands?
My guess is that qsub adds the @machine suffix because 'job_owner' needs
to be a mail address, namely the one to send job notifications to
(unless a different address is specified via -M switch).
Still, if there is a known recipe to avoid that I can implement it in
pbs_submit.sh.
Cheers,
David
--
David Rebatto
I.N.F.N. - Sezione di Milano
Via Celoria, 16 - 20133 Milano ITALY
tel: +39 02503.17623 e-mail: [log in to unmask]
URL: http://www.mi.infn.it/~rebatto
"Computer science is not about computers any more than
astronomy is about telescopes." -- Edsger W. Dijkstra
|