.
Here is the post:
thelastpickle.com/blog/2016/07/27/about-deletes-and-tombstones.html.
2017-12-05 2:01 GMT+00:00 wxn...@zjqunshuo.com :
> Got it. Thank you.
>
>
> *From:* Meg Mara
> *Date:* 2017-12-05 01:54
> *To:* user@cassandra.apache.org
> *Subject:* RE: Tombstone warnings
Got it. Thank you.
From: Meg Mara
Date: 2017-12-05 01:54
To: user@cassandra.apache.org
Subject: RE: Tombstone warnings in log file
Simon,
It means that in processing your queries, Cassandra is going through that many
tombstone cells in order to return your results. It is because some of the
TTLed
data will be purged sooner.
You could also consider drafting more efficient queries which won't hit TTLed
partitions.
Thanks,
Meg
From: wxn...@zjqunshuo.com [mailto:wxn...@zjqunshuo.com]
Sent: Sunday, December 03, 2017 7:49 PM
To: user
Subject: Tombstone warnings in log file
Hi,
Hi,
My cluster is running 2.2.8, no update and deletion, only insertion with TTL.
I saw below warnings reacently. What's the meaning of them and what's the
impact?
WARN [SharedPool-Worker-2] 2017-12-04 09:32:48,833 SliceQueryFilter.java:308 -
Read 2461 live and 1978 tombstone cells in cargts.
