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  June 2005

XROOTD-L June 2005

Subject:

Re: writing with xrdcp, redirection if server goes down

From:

Fabrizio Furano <[log in to unmask]>

Date:

09 Jun 2005 11:39:08 +0000Thu, 09 Jun 2005 11:39:08 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (111 lines)

Hi Wilko,

Wilko Kroeger wrote:
> 
> Hello
> 
> I did some test using xrdcp to write to xrootd and what happens if a data
> server goes down. I am using xrootd version 20050525-0946 for the data
> servers and redirector and 20050509-2006 for xrdcp.
> 
> The main question is:
> Should xrdcp after a data server goes down ever be redirected to a new
> data server or should it just exit ?

  The same behavior applies to all kinds of requests: if an error 
occurs,  the client goes back to the redirector and asks again what to 
do. So, xrdcp is not supposed to exit.

> That's what I assumed but as described in the two tests below the current
> behavior is different.
> 
> 
> First Test:
> ===========
> 
> For the first test writing is done via the redirector and once xrdcp
> is redirected to the data server and starts transferring data the
> xrootd on the data server is stopped.
> 
> I observed the following:
> 1) xrdcp goes back to the redirector after the data server is stopped.
> 2) the redirector tells the client to wait which ends up to about 9 mins
> 3) After waiting for 9 mins the client tries to open the file on the
>    redirector and
>    a) crashes with a core
>      or
>    b) tries to write, doesn't succeed and stops (no core)
> 
> The log files are available in:
>  /nfs/objyserv01/objy/databases/wilko/xrootd/problems/xrdcp_writeServerGoesDown
> 
> xrdcp.log : output of xrdcp
> rdr_xrdlog.log : xrootd log file of the redirector (datadevsol12)
> datadevsol02_xrdlog.log : xrootd log file of the data server
> core.3067 : core file from xrootd (the binary is
> ~wilko/bbtest/xrootd/20050509-2006/bin/xrdcp  on RHEL3)
> 
> 
> In the case that xrdcp doesn't create a core the log files are:
> xrdcp_noCore.log
> rdr_xrdlog_noCore.log
> datadevsol02_xrdlog_noCore.log
> 
> 
> In the case of writing, should xrdcp go back to the redirector, or should
> it just wait for a certain time, and if the data server isn't available
> just quit ?
> 
> 

  I am going to have a look at those. Unfortunately today I have lessons 
up to late afternoon.



> Second Test:
> ===========
> 
> For the second test the first test is run twice with a restart of
> one of the data servers in between.
> Assuming there are two data servers, DS0 and DS1, the following is done:
> 
> 1) xrdcp a new file via the redirector
> 2) xrdcp is redirected to DS0, and starts to transfer the file
> 3) xrootd on DS0 is stopped, xrdcp waits for 9 mins and then exits
>    leaving an incomplete copy of the file on DS0
> 4) xrdcp is restarted again with the same file name
> 5) xrdcp is redirected to DS1 (DS0 is still down), and starts to transfer
>    the file
> 6) xrootd on DS1 is stopped. xrdcp goes back to the redirector
> 7) xrootd on DS0 is restarted
> 8) xrdcp is redirected to DS0 and continues to transfer the file.
>    It doesn't start over writing the file but it continues where it
>    stopped in step 6, which means the file could be corrupted (e.g.:
>    in step 2 the first 100MB are transfered and in step 6 it starts
>    at an offset of 150MB).
> 
> 
> This question again is:
> Shouldn't xrdcp just give up after it failed to write the file.
> 
> If it get redirected after a data server goes down, shouldn't
> it start to write the file from the beginning?
> 
> I couldn't test the latest version of xrdcp (session id problem) and I
> don't know if the latest version behaves the same way.
> 
> 

  The latest version is supposed to behave the same way, except for the 
session id problem, which hopefully I will be able to fix quickly.
  The problem is that the system exposes something like a "relaxed" 
filesystem, where you cannot expect total adherence to what is commonly 
considered "file system semantics".

  I will have a look, and fix asap the problems I find.

  Fabrizio


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

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