Hello.
You may tell the slave to replicate updates only for the certain database
or table. See:
http://dev.mysql.com/doc/mysql/en/Replication_Options.html
Eben Goodman [EMAIL PROTECTED] wrote:
I am considering setting up replication for a loaded database that has
to perform
I am considering setting up replication for a loaded database that has
to perform thousands of heavy selects every day. I want to have a
master with one way replication to multiple slaves. But I also want to
be able to load balance connections across the multiple slaves. What
options exist
On Fri, Jan 21, 2005 at 09:21:18AM -0500, Eben Goodman wrote:
connection layer, and based on time of day or something passes a
You could use a TCP load balancer such as Balance or PEN, or you
could modify the code to randomly select a server name from a
list at connection time.
-Jason Martin
--
The easiest way, which does not need any code changes, is to set up DNS
round robin. Every time the application resolves the database domain name
it gets a random (I believe the nameserver just circulates the list) IP
back.
Atle
-
Flying Crocodile Inc, Unix Systems Administrator
On Fri, 21 Jan
We have a mySQL clustering system in the works, which will be able to
give you clustering support ( up to 32 nodes per cluster ), with full
transactions support, in a write to ALL (at the same), read from LEAST
BUSY architecture.
In other words, all nodes will be able to serve as slaves. The
