<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David, <br>
<br>
You can track the port health of any one of the two application
ports and declare that vip as unhealthy this failing it. The pdf docs
are out there on how to track that. <br>
<br>
<br>
<br>
Manolo<br>
<br>
Manu Chao wrote:
<blockquote
cite="mid:7100ed370907150115m2e2e2b4ak87c9e21753ed0bc@mail.gmail.com"
type="cite">
<div>i am sure a vendor like f5 will help you to overcome your
applications limitations<br>
</div>
<div class="gmail_quote">On Tue, Jul 14, 2009 at 4:26 PM, David
Miller <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:syslog@d.sparks.net">syslog@d.sparks.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Hi
All;<br>
<br>
I've got a situation that I'm not sure of the best way to handle.<br>
<br>
I have a pair of servers that are able to run the same application.
Caching issues make it weird though. The application writes to the
database when updates come in, and (of course) updates its own internal
cache. The servers don't update each other, however, nor do they get
updates from the database any time other than at startup. "startup" in
this case is defined as the first query that hits tomcat.<br>
<br>
What this means is that I want to run off S1 as long as its running.
And if S1 becomes unavailable I want to run off S2 until I come back
and fix things. lb-pri-servers takes care of that part.<br>
<br>
Here's the complicated part. The servers accept SSL as well for user
authentication. I need http and ssl to fail to S2 as a pair - both or
neither. We recently had application response issues where S1 was very
slow to respond, and http failed over but ssl did not. This broke the
customers ability to authenticate. We're terminating ssl on the
ServerIron 4G's and talking plaintext on port 443 to the server.
Apache is listening on 80 and 443 expecting plaintext.<br>
<br>
We've played with boolean health checks, but I haven't implemented
them. I'm concerned about separate health checks because nothing
different is being tested. It seems like a race condition would still
exist where http would fail over, but a second later the ssl check
would pass. What we need is for a single failed health check to down
the server and fail all services over to the backup.<br>
<br>
If it makes things easier, we can just skip the ssl test. A single
test for http is adequate for making sure apache is responding on the
server.<br>
<br>
<br>
Suggestions very welcome.<br>
<br>
--- David<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a moz-do-not-send="true" href="mailto:foundry-nsp@puck.nether.net"
target="_blank">foundry-nsp@puck.nether.net</a><br>
<a moz-do-not-send="true"
href="http://puck.nether.net/mailman/listinfo/foundry-nsp"
target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
foundry-nsp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></pre>
</blockquote>
<br>
</body>
</html>