ok.tech: Cassandra meetup

Working with Apache Cassandra NoSQL Storage?

May 23 Odnoklassniki invite experienced developers to their office in St. Petersburg at a meeting dedicated to working with Apache Cassandra. What is important is your experience with Cassandra and the desire to share it.
Register for an event

We in OK started using Apache Cassandra in 2010 to store photo ratings. Currently, we are the largest users of Apache Cassandra in Runet and one of the largest in Europe. We have more than a hundred different clusters used for storing various product information — classes, chats, messages, and for managing critical infrastructure data — mapping logical blocks onto large binary storage disks — one-cold-storage , one-cloud internal cloud data management etc.

In total, Odnoklassniki running Cassandra has petabytes of data on thousands of nodes. During this time, we have accumulated vast experience in administering, developing and operating solutions based on Cassandra and even developed our own NewSQL transactional database .
')
Now we would like to share all this with you - on real cases from practice and without secrets; The event will be held in the format of a lively discussion between the participants, which means that the discussion will take up most of the time. OK experts are ready to share their ideas and approaches. Oleg Anastasyev and Alexander Khristoforov will be leading the event.

What are the topics?

Exploitation:

Consider the typical configuration of nodes and clusters in different production installations. Discuss how to expand the cluster with the growth of data and load and how to replace the failed nodes with minimal effect for customers. Share the pain and systematize the popular rake. We will find out how to monitor the cluster in order to understand in advance where and what exactly is working wrong. We will address the problems of deployment of new versions of Cassandra.

Performance:

Let's try to understand what metrics to look at and what can be done to make the metrics better. Let's figure out whether to retract or not, and if so, how. Identify bottlenecks in the architecture and implementation of Cassandra and consider some engineering tricks to get around them. We will touch sore regular repair and compaction without performance degradation.

Fault tolerance:

Iron does not last forever, so accidents happen all the time, and a colleague's hand may falter and we will remove too much, so we will discuss recovery from failures of disks, machines or data centers, as well as a rollback to a consistent state from backups in case of operator errors.

Sign up and tell your friends and colleagues about the event.