I don't run any master with that many slaves, for reasons that are irrelevant to
this thread, but I know there is a point at which the slaves begin to place too
much load on the master because they are all asking to read the binlog. I don't
know what that point is exactly, but perhaps others ca
Hello,
Hmmm, I just reread your post and noticed the requirement of 50-60
slaves hanging off a single master. DRBD would NOT be the right solution
here.
-- Jimmy
Jimmy Guerrero wrote:
Hello,
Although you state that there is no requirement for near real time
synchronization, an alternative
Hi sol,
sol beach wrote:
I have limited experience with MYSQL replication; which is why I am hoping
others with more experience can answer a question or two.
Let's say I have a MASTER MYSQL database.
Let's say there are 50 - 60 other systems where I'd like to have MYSQL
running on these "slave"
Hello,
Although you state that there is no requirement for near real time
synchronization, an alternative might be to look into DRBD. Which if you
are not familiar with, is block-level replication.
See: http://www.mysql.com/products/enterprise/drbd.html
Combining DRBD with Linux Heartbeat al
I have limited experience with MYSQL replication; which is why I am hoping
others with more experience can answer a question or two.
Let's say I have a MASTER MYSQL database.
Let's say there are 50 - 60 other systems where I'd like to have MYSQL
running on these "slave" systems.
These slave system
