Question-: You are trying to repair a table using nodetool repair command, but you have found that repair is not executed on that table. What could be the possible reason? A. Because NodeSync is already enabled on the table B. Repairing disable on that table C. The node which is hosting the table is down. D. This table was already repaired 6 hours before.
Answer: A Exp: Whenever on the table if NodeSync is enabled then repair operation would be skipped for that table. Even you can enable NodeSync for entire keyspace as well. Hence running repair command for an individual table would be rejected when NodeSync is enabled.
Question-: Which of the following is/are correct for repairing table on a particular node? A. You should run when node was disconnected from the cluster for some time. B. You should run repair command at least once before gc_grace_second expire C. You have to make sure that your repair can finish before gc_grace_second window expire D. You should run repair command when node is under high utilization.
Answer: A, B, C Exp: Repair a good option for bringing data in sync on all the nodes in the cluster. But you have to be careful when you should run it and when it should get completed. So, whenever you run nodetool repair command you have to make sure that it get completed before the gc_grace_second window expire. And you also have to make sure that it should run at least once for every gc_grace_second. If cluster is under heavy utilization then you should avoid firing the nodetool repair command. Because repair command is a heavy operation and creating a Merkle tree itself is an heavy operation for a node.
Question-: Please map the following options for the Nodetool repair command.
Answer: A-1, B-2, C-3, D-4 Exp: Using the nodetool repair command you can bring replicas in sync. There is various option Available like providing end of the token whether you want to repair the full repair or not, you want repair locally on that node, or you want to repair on the particular datacenter. Similarly, you can tell that repair should be run only on this table for primary range of the token. Primary range means the token which would be owned by that particular node. • Remember full repair runs on all keyspace and on all the tables • Repair runs in parallel on all nodes with the same replica data at the same time. • You can even initiate the sequential repair. • If you want to restrict repaired local to datacenter then use the - - dc option