JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  April 2014

LCG-ROLLOUT April 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: question about CREAM "users"

From:

David Rebatto <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Thu, 17 Apr 2014 14:50:33 +0200

Content-Type:

multipart/signed

Parts/Attachments:

Parts/Attachments

text/plain (57 lines) , smime.p7s (57 lines)

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



Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
November 2023
June 2023
May 2023
April 2023
March 2023
February 2023
September 2022
June 2022
May 2022
April 2022
February 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
February 2021
January 2021
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager