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  January 2006

XROOTD-L January 2006

Subject:

Re: Host removal on the olbd manager

From:

Pavel Jakl <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

31 Jan 2006 04:01:03 +0100Tue, 31 Jan 2006 04:01:03 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (112 lines)

Hello Andy,

first of all, thanks for the quick reply.
Andrew Hanushevsky wrote:

> Hi Pavel,
>
> What release are you running. I do recall that we had some end 
> conditions that were corrected in recent releases. I am particular 
> concerned here because the current version should not be sensitive to 
> stange load values. They are generally ignored (with a message).

We are running the latest production release, i.e 20050920-0008. Maybe 
you are probably thinking over, why I did come with load values. 
Presumably one month ago, I got the same strange behavior. I have found 
in olbd manager's log file that some of nodes were delivering wrong load 
values and than the node was scheduled for removal etc.
I corrected our script for meassuring the load and everything was after 
the repair ok.

You probably mean by the current version the 20060105-0311 development 
version.

>
> Anyway, here is the expected scenario:
>
> a) A server node drops out (i.e., the redirector cannot communicate 
> with it).
> b) The redirector takes the server "offline" (i.e., scheduled for 
> removal). This means that anyone who would have been redirected to 
> that server is told to wait.
> c) The server now has 10 minutes or so (this is configurable) to 
> reconnect to the redirector.

Ok, is it a {olb.delay drop 10m}, right ?*
*

> d) After 10 minutes, the server is dropped and considered no longer to 
> be in the configuration.
> e) The server in (d), of course, is free to reconnect.
> Now, the scenario works backwards as well. The server should 
> eventually see that the redirector is no longer communicating with it. 
> This will cause the server to terminate it's redirector connection and 
> try to re-establish that connection. Older version of the olbd had 
> some problems in that code relative to flaky network connections. That 
> should no longer be the case. What does the server log show?
>
> Assuming you are running the current version, should you be able to 
> get a server in that state (i.e., it canot reconnect to the 
> redirector), then a gcore of the server along with the complete log 
> file  would be extremely helpful.

The log files are located in http://www.star.bnl.gov/~pjakl.
About 060128 19:09:30 you can the problems with a network, located in 
"rcas6132/rcas6132.olb.log.20060129".
Your mentioned scenario can be seen in rcas6150.olb.log, but the problem 
is after that.
Last record is
060128 15:54:45 001 olb_Server: Logged into xrdstar

That is before the removal in "rcas6132.olb.log.20060129" at 060128 
19:09:30 at  and then nothing.

Hope that will help you.

Pavel

>
> Andy
>
> ----- Original Message ----- From: "Pavel Jakl" <[log in to unmask]>
> To: "Xrootd Mailing List" <[log in to unmask]>
> Cc: "Jerome LAURET" <[log in to unmask]>
> Sent: Monday, January 30, 2006 4:36 PM
> Subject: Host removal on the olbd manager
>
>
>> Hi all,
>>
>> I have got very strange behavior of our installation. Let me describe 
>> it:
>> We had some problems on one of Cisco switch boards where is also 
>> connected our redirector node. There was discovered these lines in 
>> olb log file during the crash of network :
>> Example for one node:
>>
>> 060128 19:09:30 20424 olb_GetLine: Unable to read request; no route 
>> to host
>> 060128 19:09:30 20424 olb_Manager: rcas6150:1095 scheduled for 
>> removal; not responding
>>
>> This node "rcas6150" didn't recover a connection to the redirector 
>> olbd server anymore, but the olbd proccess is stil running on that node.
>> And when someone tried to request the file from that node then he 
>> wasn't redirected to that node, even the file is there.
>> If the olbd process is restarted on that node, everything is in on 
>> order and the user is redirected to that node and file is opened.
>>
>> You can simulate this strange behavior by giving wrong numbers (means 
>> value greater than 100 etc.) of load, io etc. to redirector node. 
>> Then node is scheduled for removal ....
>>
>> Thanks for a advice
>> Let me know if you need something
>> Pavel
>>
>>
>>



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