Ok I gotcha...how about catching the specific exception raised when the
DB does its switchover and manually flush DB connections?

Stace

  _____  

From: Peter Amiri [mailto:[EMAIL PROTECTED]
Sent: December 1, 2003 2:54 PM
To: CF-Talk
Subject: RE: Optimal CF Server settings w/SQL Server Cluster

Stace,

It's my understanding the the MS SQL Server cluster does this for you.
Althought each of the individual servers have their own set of IP
addresses. A virtual SQL Server is also created with it's own ip. All
the CF Servers are pointed to the virtual SQL Server. When a SQL Server
fail over occurs the CF Servers continue to communicate to the database
through the same ip addresss. So therefore a seperate VLAN to achive the
same thing shouldn't be needed. I may be wrong though? I suspect if I
wait for the five minute timeout to occur the old connections will get
killed and new ones will be created which would then work without a
hitch. I can't afford the 5 minutes of dead time though. I am wondering
how much of a savings Maintain Connections provides and whether we
should just nix that options which should solve the problem.

-Peter Amiri
[EMAIL PROTECTED]
MySpace.com

-----Original Message-----
From: Stacy Young [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 11:35 AM
To: CF-Talk
Subject: RE: Optimal CF Server settings w/SQL Server Cluster

I'm no expert in this area but if by chance you have switching
capabilities in your topology (Alteon or what-not)...create a vlan for
the database cluster and expose that to the CF servers via a single
network address. That way CF is always bound to a static virtual server
address...no matter which database cluster member is operating behind
the scenes.

Stace

  _____  

From: Peter Amiri [mailto:[EMAIL PROTECTED]
Sent: December 1, 2003 2:30 PM
To: CF-Talk
Subject: Optimal CF Server settings w/SQL Server Cluster

I have a few questions regarding server settings in the following
environement:

CF 5.0 cluster with 5 servers in the farm
MS SQL Server cluster - Raid 10 array connected to both servers with hot
fail over
The application gets about 7 million page impressions per day

I want to what the optimal settings should be for data sources settings.
In particular Maintain Connections and Timeout settings. Currently
maintain connections is set to yes and timeout is set to 5 minutes. But
when the SQL server locks up for whatever reason and fails over to the
backup server the CF queries just start to queue up. In other words it
apears that maintaining connections open by CF some how does not get
updated to the newly live box. Before resorting to turing off maintain
connections I wanted to know if anyone has had much success with CF and
SQL clusters.

-Peter Amiri
[EMAIL PROTECTED]
MySpace.com

  _____
  _____

  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to