On Wed, 5 Dec 2001, Ollie Cook wrote:
> mysql_servers = set1/host1::3306/database1/user1/password1\
> set1/backup-host1::3306/database1/user1/password1\
> set2/host2::3306/database2/user2/password2\
> set2/backup-host2::3306/database2/user2/password2
> This would still allow for redundancy, but still cut down on the
> erroneous connections to database which have no hope of answering
> the query.
Hm. I could live with that, along with a certain amount of pain.
Again: If you encounter performance problems on host1, put in another cpu.
If you encounter disk space problems, put in disks and increase the
respective logical volume [or deal with disks, mountpoints and syslinks if
your OS is not lvm capable]. At least it appears as if triggering a little
SQL error msg does worry you you have a rather high volume site - so you
should be able to invest in hardware instead of tweaking software in a
doubtful direction.
The software's job, however is to be as simple as possible.
Experience tells us that software / site design changes provoke failures.
But I've never seen a service failing because someone added diskspace ;)
Maybe my view on this is too much HA-coloured, but at least this is what I
think.
Someone else's opinion?
Regards,
Volker
--
V. T. Mueller Freiburg, Germany vtmue (at) uni-freiburg.de
"problems are just opportunities in work cloth"
