all data everywhere
•Download as PPT, PDF•
0 likes•751 views
MySQL's replication system has been a core feature often touted for scaling (sort of) and redundancy (sort of). I'll describe a client's extensive use of MySQL replication (they have more than 200 MySQL instances replicating to one another) as a reference for the many uses and misuses of replication.
![[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],www .BlueGecko . net](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to all data everywhere
Similar to all data everywhere (20)
More from sarahnovotny
More from sarahnovotny (10)
Recently uploaded
Recently uploaded (20)
all data everywhere
- 1. MySQL replication (all data everywhere; is it a good idea?) sarah novotny – sarah@bluegecko.net MySQL and LAMP services www .BlueGecko . net
- 7. www .BlueGecko . net
- 9. www .BlueGecko . net And now we come to rings
Editor's Notes
- Not locked into proprietary space… many options. Based from the same code tree Lib mysql vs lib drizzle – licensing gotcha libmysql gpl libdrizz bsd drizzle Maria Our delta Google patches Percona xtradb
- Google patches include a better malloc And completely changed locking
- Choose 5.1 or 5.4 only if you need the featuresets.
- Much performance pain come into play with lock contention
- Understand
- Understand
- Understand
- Understand
- API SHOULD KNOW THE DIFF proxy as an option if API not possible. scale writes. write own interfaces? check on it. btree index larger than memory -- writes get _slow_ Memcached – good for short lived data and caching wafflegrid -- patches to mysql -- innodb bufferpool over memcached
- LVM and slaves give easy opportunities for creating clones for testing
- •❑ disk•❑memory•❑up/down•❑cachehit -- baseline defiinition•❑replication •❑ mktablesync•❑mkchecksum