Quote:
Originally Posted by darksoul
writes always go to the master with replication. I doubt they have multi master replication , its not really doable without a heck of modifications (consider that vb is close source and you're kinda limited).
So, I'm assuming they have a one master - many slaves replication. Considering the database size keeping too many slaves its counter productive.
Now, if you've worked with huge databases and replications you know that the slaves brake pretty often due to invalid data or other replication errors. I guess you can imagine what a pain in the ass would be to resync a dead slave.
|
I meant are reads and writes seperated, writes to master, reads from slave.
I think you are overestimating the size of the GFY database especially when
considering that it was compacted by purging historical records.
I think the main problem is in the countless modifications they've tried over
time to solve the problem. Anyway it doesn't really matter coz obviously
they're not interested in fixing it anyway
