Question

__________ can be configured per table for non-QUORUM consistency levels.
Read damage
Read repair
Write repair
Write damage

Answer 1

⛦Hᴇʀᴇ Is Yoᴜʀ Aɴsᴡᴇʀ⚑
▬▬▬▬▬▬▬▬▬▬▬▬☟

▶"Read repair" can be configured per table for non-QUORUM consistency levels.

________________________⤵


❖ It provides an opportunity for consistency improvement.

❖ It is an important component of keeping data consistent in a Cassandra cluster.

❖ As a background process, read repair generally puts little strain on the cluster.

❖ Cassandra sends a digest request to each replica not directly involved in the read.

❖ It serves as an anti-entropy mechanism during read path.

❖ It Ensure that all replicas have the most recent version of frequently-read data.

❖ If you do change the value, especially if you increase it, you might need to force read repair.

_________
Thanks...✊

Answer 2

Read repair can be configured per table for non-QUORUM consistency levels.

Explanation:

• Whenever a read query found any inconsistencies in its results of consistent level higher than ONE or LOCAL_ONE, read repair will get initiated.  

• These read repair processes will run in the block application and foreground application programs until this read repair process got completed.  

• If the replicas are found to be inconsistent, then the coordinator issues will write to the out of date replicas in order to update the rows to the most recent values.