Hi,

The blogs.cisco.com site is a very high traffic site. The Database was crashed suddenly. So What DB & other settings need to changed in order to handle the very high traffic on the site.

We are using the EE v 1.6.3, build: 20080319

Thanks.

Hi, tsoares -

When you say that it crashed - what do you mean?  For instance: did the server the database resides on run out of hard-drive space? If so, no settings can help there; that would be a hardware issue.

Did you get error messages? What were the symptoms?

Once we know that information, we’ll be in a much better position to help you out. As a note, ExpressionEngine itself can handle very high traffic sites, but it is very much a matter of hardware and server infrastructure and tuning for high-traffic dynamic sites.

Hi Lisa,

Here is error message we got.

“Database Error: Unable to connect to your database. Your database appears to be turned off or the database connection settings in your config file are not correct. Please contact your hosting provider if the problem persists.”

The Admin -> General -> Database Settings—> Database connect setting : non-persistent selected.

Also Cache query is enabled.

Pls let me know what else can cause this issue.

Thanks

Hi, tsoares - yes, that does mean the database became unavailable.  The best way to track why it was unavailable would be to speak with your server administrator who can go back and look at the error logs and find out what may have happened.  Knowing only that the the database went down isn’t quite enough; we need to know what symptoms brought it down.  It could even have been normal maintenance - right now it would all be guess-work, without more information from your administrators.

Hi Lisa,

The Sysadmin says, there are no related errors to this message in the apache error log.

They have sent me the error log and I have to go thru it to verify there is any. I will also check with them if the database was as part of normal maintainence.

Thanks for the quick answers/ideas on the issues.

Thanks for getting back to us, please let us know what you find.