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  2005

LCG-ROLLOUT 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Forward requirements to local batch system (fwd)

From:

David Rebatto <[log in to unmask]>

Reply-To:

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

Date:

Tue, 27 Sep 2005 09:28:04 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (84 lines)

Burke, S (Stephen) ha scritto:

>LHC Computer Grid - Rollout 
>  
>
>>[mailto:[log in to unmask]] On Behalf Of Charles Loomis
>>    
>>
>said:
>  
>
>>>1) Keep the current syntax, allow matching against multiple 
>>>      
>>>
>>subclusters,
>>    
>>
>>>and pass the subcluster name to the batch system.
>>>      
>>>
>>This is not a solution to the problem.
>>    
>>
>
>It's a solution to part of the problem, i.e. that currently jobs may
>avoid sites even if only 1 WN out of 500 doesn't match the requirement,
>because you have to publish the most restrictive limit.
>
>  
>
>>I would instead opt for a hybrid approach of 2) and 3).  
>>Allow people to 
>>define parameters like in 3) and have whatever processes the 
>>final JDL 
>>combine those with any explicit requirements to arrive at the full 
>>expression.  Only those limits given separately would be 
>>passed to the local batch system.
>>    
>>
>
>Yes, that doesn't sound too bad - but in itself it wouldn't solve the
>above problem, so you might still want to think about doing subclusters
>properly, or else changing the glue schema to go back to max/min values.
>
>Stephen
> 
>  
>

Hi,
my idea was more or less the option 3) proposed by Stephen. But, as he 
said, this doesn't solve the underusage problem created by having the 
min values published in the GRIS. Anyway, if we go with a max/min 
schema, or if we publish only max values, we have to face another 
problem: how do we handle jobs dispatched to a CE when there are no free 
nodes matching the requirements (e.g. because they are busy)?
The CE could reject it and the WMS retry mechanism would submit it 
somewhere else, but this sounds very inefficient.
Another solution would be that the CE keeps the job queued until a 
suitable node is free, but this would kill any hope for the WMS to make 
any intelligent decision, as this additional queueing time would not be 
visible in the glue schema.
A third option could be the implementation of a direct WMS <-> CE 
negotiation before the actual job submission. This would require some 
completely new code on both WMS and CE, and would be even heavier than 
the simple check with the CE GRIS which LCG wanted removed from the 
brokers...

Sorry if you already discussed this problem, I've tried to read all the 
messages in the thread but I could still have missed something...

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

"There are 10 kinds of people in the world:
those who understand binary and those who don't..."

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