LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


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

XROOTD-L Home

XROOTD-L Home

XROOTD-L  November 2004

XROOTD-L November 2004

Subject:

Re: Status of xrootd from the skim production perspective

From:

Peter Elmer <[log in to unmask]>

Date:

24 Nov 2004 12:50:29 +0100Wed, 24 Nov 2004 12:50:29 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (100 lines)

  Hi Remi,

On Tue, Nov 23, 2004 at 08:28:59PM -0800, Remi Mommsen wrote:
> Not working:
> - removing directories

  For the moment this doesn't work. I'll add it to the known problem list,
but it isn't considered critical.

> With the load balancer (oprserv08)
> ==================================
> 
> - reading collections with standard access methods works *except* for  
> files written in the last 8(?) hours when the load balancer was asked  
> for the file before it did exist. This collection was copied on  
> bbrprod01 and KanCollUtil finds it:
> 
> KanCollUtil  
> root://bbrprod01:1094//prod/store/SPskims/R14/16.0.1a/BCharmoniumToHad/ 
> 23/BCharmoniumToHad_2379
> root://bbrprod01:1094//prod/store/SPskims/R14/16.0.1a/BCharmoniumToHad/ 
> 23/BCharmoniumToHad_2379 (48609 events)
> 
> but asking the load balancer does not return the file:
<....>

  This is presumably because you are xrdcp-ing the file directly to an
individual machine. When you switch to copying things in via the load
balancer itself, this should not be a problem. Why aren't you copying
things into the buffer via the load blanacer? (i.e. what is the last
outstanding problem for doing that?)

> Not working at all:
> - XrdClientAdmin::XrdExistFiles, XrdClientAdmin::XrdDirList and  
> XrdClientAdmin::XrdGetChecksum just look on the load balancer itself,  
> i.e. they do not find anything by definition

  Andy committed a fix for this (server side) last night. I'll make a
version later today which can be started.

> - xrdcp, XrdClientAdmin::XrdChmod and XrdClientAdmin::XrdRm hang:
> 041123 16:36:20 001 Xrd: SendGenCommand Server  
> [oprserv08.slac.stanford.edu:1094] requested 5 seconds of wait
> 041123 16:36:25 001 Xrd: SendGenCommand Server  
> [oprserv08.slac.stanford.edu:1094] requested 5 seconds of wait
> 041123 16:36:30 001 Xrd: SendGenCommand Server  
> [oprserv08.slac.stanford.edu:1094] requested 5 seconds of wait
> 041123 16:36:35 001 Xrd: SendGenCommand Server  
> [oprserv08.slac.stanford.edu:1094] requested 5 seconds of wait
> 041123 16:36:40 001 Xrd: SendGenCommand Server  
> [oprserv08.slac.stanford.edu:1094] requested 5 seconds of wait
> 041123 16:36:45 001 Xrd: SendGenCommand Server  
> [oprserv08.slac.stanford.edu:1094] requested 5 seconds of wait

  It sounds like this one should also be fixed with the new server version.

> In summary we are close to get the production going if we talk directly  
> to individual servers. This is clearly less than we wished for. Load  
> balancing is done on a random basis, not taking server load and disk  
> space into consideration. Finding files, getting checksums and removing  
> files requires asking all servers. This increases the overall load on  
> the system.

  Let's see if the latest round of fixes allow you to do everything via
the load balancer...

> In general a lot of functionality is implemented on the client side  
> which IMHO should be provided by the server: For example xrdcp issues  
> for each directory a mkdir command, instead just asking the server to  
> create the whole path. 

  There are two things here:

   o The "mkdir -p" type functionality. This isn't there, but Andy says he
     will add it.

   o The fact that the mkdir has to be done at all (one could just have that
     happen automatically any time a file is opened for write if some bit
     is set). Andy also will this possibility, too.

> As currently no wildcard operations work, we  
> need to get a list of files from the server and then ask the server to  
> remove each file individually.

  This shouldn't be a big deal. Actually I don't understand why you
need to ask the server for the list of files. Don't you already know that
as part of the skim bookkeeping anyway? Or do you mean: we need to get
the list of servers the files are on since rm wasn't working via the load
balancer and then delete them manually? (That shouldn't be a problem now
as mentioned above.)

                                   Pete

-------------------------------------------------------------------------
Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22) 767-4644
Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
-------------------------------------------------------------------------


Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 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
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 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
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
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 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
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

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

Privacy Notice, Security Notice and Terms of Use