Consistency Level











Comments

Post a Comment

Popular posts from this blog

Peer to Peer Architecture

   Peer to Peer Architecture in Apache Cassandra   In Cassandra’s peer-to-peer architecture, every node in the cluster is equal, meaning there is no single master node that controls other nodes. Instead, all nodes work together to handle read and write requests, replication, and data distribution. This allows Cassandra to achieve high availability and fault tolerance. Here’s how this architecture works: Key Features of the Peer-to-Peer Architecture: 1.  Decentralized Design (No Master Node): There is no master or primary node in Cassandra. All nodes in the cluster are peers, which means that they can perform the same tasks (like handling read/write requests, holding replicas, and distributing data). This eliminates the risk of a single point of failure and makes the system more fault-tolerant. 2.  Data Distribution: Data is distributed across nodes in the cluster based on a hashing function. Each node is responsible for a specific range of data, known as its tok...
Read more

Virtual Nodes in Ring

Virtual Nodes in Cassandra Ring In Apache Cassandra, virtual nodes (vnodes) are a way to divide the token range into smaller pieces and assign multiple token ranges to each node in the cluster.   What are Virtual Nodes (vnodes)? In the traditional Cassandra architecture, each node was responsible for a single, contiguous token range. This made data distribution and rebalancing more difficult when nodes were added or removed from the cluster because large ranges had to be reassigned. With vnodes, instead of assigning a single, large token range to a node, each node is assigned multiple, smaller token ranges. By default, Cassandra assigns 256 virtual nodes per physical node. This allows the total token space to be divided into many smaller chunks that are spread across the cluster. Example:   Instead of Node A owning the token range from zero to 500, Node B owning 500 to 1000, and so on, each node gets assigned multiple, smaller ranges. One node could own small token ranges li...
Read more

Read Repair Chance

Image
Read Repair Chance When a read request is made with consistency as ALL   Coordinator Node send the data request to nearest node   Coordinator Node send the checksum request from replica node Once it receives the responses it checks all the checksum values. If they are all same as below value 23 If. Values are different as below from replica nodes Coordinator nodes checks the checksum which has the latest timestamp , it discards the data from replica node which has stale data. Coordinator node sends the correct data on the replica node on which data is deleted  
Read more