Scale read workload by sharing data files of InnoDB
The original MySQL provides an ability that if innodb_read_only is turned on, you can setup multiple instances based on same data file. But this approach will prevent all data changes, which is unpractical for most applications. In this session, I'll share how we change InnoDB to make it possible to scale out read only workload by sharing data files, but still provides all types of workload that a normal MySQL allows. More specifically, we'll discuess: * Basic Architecture: physical replication, shared data/log files, etc... * Transaction Management on read only instance: MVCC, Isolation, etc.. * Buffer Pool Management: cache invalidation, data consistency between cache and physical files * Failover between primary server and read only server. Note that this talk is all about internal changes of InnoDB, so having a basic knowleges of redo log, undo log, read view and buffer pool management will be helpful.
Database Developer, Alibaba
I joined Alibaba in June 2011 and work on MySQL since then. My work includes: Improve the performance of MySQL, develop new features according to requests from our DBA team, and also fix bugs we encountered on production environment. Outside working hours , I like to investigate & test new versions of MySQL and file bugs.