title: Tombstone vs nodetool and repair
body: <p>I inserted 10K entries in a table in Cassandra which has the TTL of 1 minute under the single partition. </p>
  
  <p>After the successful insert, I tried to read all the data from a single partition but it throws an error like below,</p>
  
  <pre><code>WARN  [ReadStage-2] 2018-04-04 11:39:44,833 ReadCommand.java:533 - Read 0 live rows and 100001 tombstone cells for query SELECT * FROM qcs.job LIMIT 100 (see tombstone_warn_threshold)
  DEBUG [Native-Transport-Requests-1] 2018-04-04 11:39:44,834 ReadCallback.java:132 - Failed; received 0 of 1 responses
  ERROR [ReadStage-2] 2018-04-04 11:39:44,836 StorageProxy.java:1906 - Scanned over 100001 tombstones during query 'SELECT * FROM qcs.job LIMIT 100' (last scanned row partion key was ((job), 2018-04-04 11:19+0530, 1, jobType1522820944168, jobId1522820944168)); query aborted
  </code></pre>
  
  <p>I understand tombstone is an marking in the sstable not the actual delete.</p>
  
  <p>So I performed the <strong>compaction</strong> and <strong>repair</strong> using <strong>nodetool</strong> </p>
  
  <p>Even after that when I read the data from the table, It throws the same error in log file. </p>
  
  <p>1) How to handle this scenario? </p>
  
  <p>2) Could some explain why this scenario happened and Why not the compaction and repair didn't solve this issue? </p>