Question : In your node Cassandra cluster you see, that most of data is going to particular node only and others are sitting idle. This is known as...
1. vnode
2. Bad Partitioning
3. Hot Spot
4. Dump spot
Correct Answer : 3 Explanation: When token are not evenly assigned in Cassandra cluster and all the write goes to specific nodes in cluster. Which causes single node to be heavily loaded and Cassandra cluster performance will degrade. This is known as a Hot Spot issue
Question : You see, your node Cassandra cluster has a evenly distributed token. But still there is a Hot spot problem, how can it be solved? 1. By adding new node in the cluster.
2. re-arranging the token in cluster
3. with the help of virtual nodes
4. It cannot be solved
Correct Answer : 3 Explanation: By adding additional node and re-shuffling the token range can solve the problem of Hot spot but they cannot be solved permanently or they can create another issues. The best solution to solve this problem is using vnode or virtual node.
Question : What is true, with regards to vnode/virtual node
A. virtual nodes allow us to create individual smaller token ranges per node and it breaks up these ranges across the cluster B. Before Cassandra 3.0, vnode have 256 ranges per node C. past Cassandra 3.0, there are much more token ranges per node (more than 256) D. past Cassandra 3.0, it's much less, and it's configurable by the user (less than 256)
1. A,B,C 2. B,C,D 3. A,C,D 4. A,B,D 5. A,B,C,D
Correct Answer : 4 Explanation: virtual nodes allow us to create individual smaller ranges per node, and it breaks up these ranges across the cluster. Now, each single node doesn't have all the data. By default, pre-3.0, it is 256 ranges per node. Now, past 3.0, it's much less, and it's configurable by the user.
Prior to Cassandra 1.2, you had to calculate and assign a single token to each node in a cluster. Each token determined the node's position in the ring and its portion of data according to its hash value. In Cassandra 1.2 and later, each node is allowed many tokens. The new paradigm is called virtual nodes (vnodes). Vnodes allow each node to own a large number of small partition ranges distributed throughout the cluster. Vnodes also use consistent hashing to distribute data but using them doesn't require token generation and assignment.