title: Why is forcing major compaction on a table not ideal?
body: <p>Consider a scenario where a table partitions with thousands of deleted rows. When reading from the table, Cassandra has to scan over thousands of deleted rows before it gets to the live rows.</p>
  <p>A common workaround is to manually run a compaction on a node to forcibly get rid of tombstones.</p>
  <p>What are the downsides of forcing major compaction on a table (with <code>nodetool compact</code>) and what is the best practice recommendation?</p>