addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Taking the pain out of repairs

Taking the pain out of repairs

Incremental Repairs, added in Cassandra 2.1, are designed to take the pain out of repairing your cluster. By taking advantage of the work performed by previous repair sessions, each new session need only consider new data which can reduce the time and computing resources needed. Even with these advances repairs can still seem like an "Advanced Cassandra" topic. 

In this talk Mick Semb Wever, team member at The Last Pickle, will explain why we need repair, how it works, when to do it, and how Incremental Repairs may take the pain away.


Mick Semb Wever works at The Last Pickle helping customers deliver and improve Apache Cassandra based solutions. Prior to TLP he spent seven years at building their Microservices platform utilizing Apache Cassandra, Hadoop, Spark and Kafka. He is the PMC Chair for Apache Tiles, a DataStax MVP for Apache Cassandra, and an active participant in the Open Source community.


DataStax and RoZetta Technology.


Level 4/55 Harrington Street, The Rocks, 2000


6:00 - Pizza & Drinks

6:15 - Presentation & discussion

Join or login to comment.

15 went

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy