If you can't read please download the document
Barcamp MySQL
Embed Size (px)
DESCRIPTION
My Barcamp Brussels 3 presentation on getting the most out of MySQL
Citation preview
2.
-
- Linux and Open Source Consultant
-
- Senior Consultant/CTO @ x-tend.be
3.
4.
- Your Application is Too Big
-
- You really need more power
5.
- Historical MySQL Clustering
-
- Application needed to be modified
6.
-
-
-
- Are we sure about the replicated data ?
-
-
-
- Support for myisam cluster
-
-
-
- HA , Scalablilty, Manageability
7.
- - Is an Engine such as MyISAM, InnoDB
8.
-
- Shared Nothing Clustering
-
- Main Memory Engine only !
-
-
- All data lives in memory !
-
-
- Disk Based is in progress
9. `
-
-
-
- Any singleserver can fail
-
-
-
- often multiple failures also survive
- No extra hardware (expensive) required
- No dependency on other nodes
10.
-
- Data is horizontally partitioned over the nodes
- - Each node is in charge of only a piece of
- - Data can be read in parallel
- - E.g 4 data nodes could have 4 data
- fragments with each of the data.
- 4Gb database requires 1Gb on 4 nodes
11.
-
- Data is replicated to NrOfReplicas Nodes
-
- Guaranteed at Commit time to be present
-
- - Automatic node takeover.
-
- If you only have 2 nodes and you need to
-
- store 2 Gb of data you need 2Gb of memory
12.
-
- Everything (data + indexes) are in Memory !
-
- Available memory restricts database size
13.
14.
-
- ndb_mgmd the management nodes
-
- ndbdthe cluster storage nodes
-
- mysqld, the traditional MySqld talking to
-
- Can run on the same or different servers
-
- For true HA ndb_mgmd cant be on one of
15.
-
- In charge of cluster config
-
- Only Needs to be running when nodes
-
-
- Master / slave Arbitration
16.
-
- Standard MySQL node compiled with ndbd
-
- Can use other storage engines
-
- Can be enabled by default
17.
-
- Has to be a multiple of NrOfReplicas
18.
19. Pulling Traffic to the Cluster
- Advertise routing (ripd/vrrpd/bgpd)
20.
- Database Size = Required Memory
- Indexes still live in memory
21.
22.
- Use MySQL Cluster as frontend
23.
- What else with Large data ?
- Partition your data manually
- Use MultiMaster Replication
24. KrisBuytaert http://www.x-tend.be/~kb/blog/ Contact &
Further Reading :