Question-: In Cassandra cluster when repairs are initiated? A. While reading the data if it was found that data is not in sync then repair would be initiated. B. You can manually initiate using the nodetool repair command. C. Based on the property configure read_repair_chance it can randomly repair the node. D. Once in 10 days repair would be done at least once.
Answer: A,B,C Exp: There are various event for option through which nodetool repair can be initialized some of them are as below • while reading the data if it was found that replica is not in sync with another node then repair would be initialized for that replica. • if somebody manually initiate the command using the node tool. • or if you are configuring the property read_repair_chance then based on that randomly the node would be repaired.
Question-: Which of the following parameter, would be used for defining the data validation for repair frequency with the NodeSync? A. rate_in_kb B. deadlinbe_target_sec C. gc_grace_seconds D. nodesync_repeat
Answer: B
Explanation: Table which has NodeSync enabled Has a property like deadlane_target_sec, Which is the time difference of the maximum time for validating the same data again. If this parameter is made in all parts of the that particular table are validated at least once or twice and data would be repaired.
Remember that this parameter that deadline_target_sec should always be less than GC Grace period (gc_grace_sec).
Question-: Which of the following parameters are related when configuring NodeSync to be completed in the given time frame?
A. deadline_target_sec B. rate_in_kb C. gc_grace_sec D. rate_in_sync
Answer: A,B
Explanation: NoodeSync try to validate all the tables within their respective deadline, but it depends on what rate you have configured. Suppose you have 100 GB of a table size where you have configured deadline_target_sec=10 and rate_in_kb is set to 10 MB per second, then validation will not happen quickly and you may see following warnings in the system.log file.
• Rate in KB is too low to validate all the tables within their deadline. • Rate in KB cannot be sustained by the node, if it is set very high
Remember NodeSync service is a per node service, hence parameter rate_in_kb is also set for node. Which defines maximum number of bytes per second used for validating your data for that particular table.