re:Invent 2012 Optimizing Cassandra
•Download as PPTX, PDF•
3 likes•2,129 views
AWS re:Invent 2012 presentation on Optimizing Cassandra usage at Netflix. Overview of Netflix Open Source projects. Gregg Ulrich, Ruslan Meshenberg.
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (17)
More from Ruslan Meshenberg
More from Ruslan Meshenberg (11)
Recently uploaded
Recently uploaded (20)
re:Invent 2012 Optimizing Cassandra
- 2. Netflix AWS Cassandra
- 4. Netflix API – Growth in requests 25 Requests in Billions (per day) 20 15 10 5 0 Data Center Capacity
- 9. us-west-2 1c 1c 1a 1e 1d S3 1b 1d 1e 1b 1c Durability (Quorum) 1c One instance: 1c 1a 1a Availability zone: Replica set: 1e 1d 1c 1b 1d 1e 1b 1c 1c S3 1a S3 us-east-1 eu-west-1
- 23. 23
- 24. 24
- 25. 25
- 26. 26
- 27. Client Writes/s by node count – Replication Factor = 3 1200000 1099837 1000000 800000 600000 537172 400000 366828 200000 174373 0 0 50 100 150 200 250 300 350
- 30. 50 Number of production clusters 15 Number of multi-region clusters 4 Max regions, one cluster 101 Total TB of data across all clusters 780 Number of Cassandra nodes 72/32 Largest Cassandra cluster (nodes/data in TB) 250k/800k Max read/writes per second on a single cluster
- 36. We are sincerely eager to hear your FEEDBACK on this presentation and on re:Invent. Please fill out an evaluation form when you have a chance.
Editor's Notes
- … Developer in house …Quickly find problems by looking into codeDocumentation/tools for troubleshooting are scarce… repairs …Affect entire replication set, cause very high latency in I/O constrained environment… multi-tenant …Hard to track changes being madeShared resources mean that one service can affect another oneIndividual usage only growsMoving services to a new cluster with the service live is non-trivial… smaller per-node data …Instance level operations (bootstrap, compact, etc) are faster