How configuring LVS not to shut down current RTSP session if the monitoring scripts returns an unexpected answer?

"Lienard Anne" <[email protected]> Tue, 15 Jan 2008 15:01:56 +0100
Newsgroups gmane.linux.redhat.piranha
Message-ID <BD939068A237684292AF8E6FFB365F1302247D7D@CESSSMAIL01.eu.thmulti.com>
This is a multi-part message in MIME format.

--===============1341739813==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8577F.307B76AE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8577F.307B76AE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

=20

We use LVS on Redhat 5.1 (2.6.18-53.el5) on 2 IBMS X3650 servers. Here
are the RPM versions:

ipvsadm-1.24-8.1.i386.rpm

system-config-cluster-1.0.50-1.3.noarch.rpm

piranha-0.8.4-7.el5.i386.rpm

=20

The two servers are configured as one master / one backup.=20

=20

They are also configured to hold the virtual service RTSP. This service
is load balanced with round robin method between the two RTSP gateways
(the real servers are also the two X3650 servers).

=20

When a RTSP session is set up, LVS selects the RTSP gateway, the session
is initialized by accessing database and then Video server.

=20

When established, the RTSP session only access the video server for
streaming.

=20

The monitoring script chosen to monitor the real server is: RTSP access
test and database access test.

=20

If the database is no more available, the monitoring script returns a
bad answer and the service goes down: the process nanny shuts down the
IP:PORT session.

Because of this shutting down, all the current streamings on this RTSP
gateway stop.

=20

Here are the logs:
Jan 8 17:28:17 FHS1 nanny[10420]: Trouble. Recieved results are not what
we expected from (172.20.253.215)
Jan 8 17:28:17 FHS1 nanny[10420]: shutting down 172.20.253.215:554 due
to connection failure

=20

For robustness reason, we need that nanny process prevents new
connections when the database goes down. But we need that current RTSP
sessions go on, NOT STOP.

Is there any way not to shutdown current connections when the monitoring
scripts answer not what expected? Dynamically change weight of the real
servers to zero for example?

=20

Thank you for your answer.

=20

Anne

=20

=20

=20


------_=_NextPart_001_01C8577F.307B76AE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Verdana;
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Verdana;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Hello,<o:p></o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>We use LVS on =
Redhat 5.1
(2.6.18-53.el5) on 2 IBMS X3650 servers. Here are the RPM =
versions:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>ipvsadm-1.24-8.1.i386.rpm<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>system-config-cluster-1.0.50-1.3.noarch.rpm<o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>piranha-0.8.4-7.el5.i386.rpm<o:p></o:p></span></font=
></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>The two =
servers are
configured as one master / one backup. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>They are also
configured to hold the virtual service RTSP. This service is load =
balanced with
round robin method between the two RTSP gateways (the real servers are =
also the
two X3650 servers).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>When a RTSP =
session is
set up, LVS selects the RTSP gateway, the session is initialized by =
accessing
database and then Video server.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>When =
established, the
RTSP session only access the video server for =
streaming.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>The =
monitoring script
chosen to monitor the real server is: RTSP access test <b><span
style=3D'font-weight:bold'>and</span></b> database access =
test.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>If the =
database is no
more available, the monitoring script returns a bad answer and the =
service goes
down: the process nanny shuts down the IP:PORT =
session.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Because of =
this
shutting down, all the current streamings on this RTSP gateway =
stop.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Here are the =
logs:<br>
Jan 8 17:28:17 FHS1 nanny[10420]: Trouble. Recieved results are not what =
we expected
from (172.20.253.215)<br>
Jan 8 17:28:17 FHS1 nanny[10420]: shutting down 172.20.253.215:554 due =
to
connection failure<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>For =
robustness reason,
we need that nanny process prevents new connections when the database =
goes
down. But we need that current RTSP sessions go on, NOT =
STOP.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Is there any =
way not
to shutdown current connections when the monitoring scripts answer not =
what
expected? Dynamically change weight of the real servers to zero for =
example?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Thank you for =
your
answer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Anne<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C8577F.307B76AE--


--===============1341739813==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Piranha-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/piranha-list
--===============1341739813==--