Cassandra Compaction vs Repair vs Cleanup

After posting the question and reading this and that article, I still don't understand the relationship between these three operations -

  • Cassandra Compaction Tasks
  • nodetool repair
  • nodetool cleanup

Is it possible to handle the recovery task during the execution of the compaction task or to perform the cleaning during the execution of the compaction task? Is cleaning an operation that must be performed weekly as a repair? Why should the restore operation be performed manually, and this does not apply to Cassandra's default behavior?

What are the basic rules for secure cluster maintenance?

+4
source share
1 answer

A cleanupis a seal that simply removes things outside the range of tokens (s). A repairhas a โ€œVerification Sealโ€ to build a merkle tree for comparison with other nodes, so the part nodetool repairwill have a seal.

Is it possible to handle the recovery task during the execution of the compaction task, or to perform the cleaning during the execution of the compaction task?

There is a common pool for trade-offs between regular copies, patches, cleanups, scrubs, etc. This is the parameter concurrent_compactorsin the cassandra.yaml file, which by default contains a combination of the number of cores and data directories: https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/config/DatabaseDescriptor .java # L572

- , ?

, .

, ?

, gc_grace. https://issues.apache.org/jira/browse/CASSANDRA-10070 Cassandra, .

?

() :

  • ( : / ).
    • "" ( "Opps deleted customer" ) . .
  • , Repair , gc_grace .
  • , .
+12

All Articles