Working with Apache Cassandra NoSQL storage?
May 23 Odnoklassniki invite experienced developers to their office in St. Petersburg for
We are OK
In total, in
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 live discussion between the participants, which means that the discussion will take up most of the time.
What will be the topics?
Exploitation:
Consider typical node and cluster configurations in various production installations. Let's discuss how to expand clusters with increasing data volumes and load, and how to replace failed nodes with minimal impact on customers. Let's share the pain and systematize the popular rake. Let's figure out how to monitor the cluster in order to understand in advance where and what exactly is not working. Let's touch on the problems of deploying new versions of Cassandra.
Performance:
Let's try to understand what metrics to look at and what can be tuned to make the metrics better. Let's figure out whether to re-trace or not, and if so, how. Let's identify bottlenecks in Cassandra architecture and implementation and look at some engineering tricks to work around them. Let's touch on sore regular repair and compaction without performance degradation.
Fault tolerance:
Hardware does not last forever, so accidents happen all the time, and a colleagueβs hand can tremble and we will remove the excess, so we will discuss recovery after failures of disks, machines or data centers, as well as rollback to a consistent state from backups in case of operator errors.
Source: habr.com