Hi All,
I'm using the SSTable with Size Tired Compaction Strategy with
10 days gc grace period as default.
And sstablemetadata command shows Estimated tombstone drop times
As follows after minor compaction on 9th Dec, 2018.
(excerpt)
Estimated tombstone drop times:%n
1510934467: 2475 * 201
SSTable
containing the tombstone can the tombstone be removed.
On 11 December 2017 at 01:08, tak...@fujitsu.com<mailto:tak...@fujitsu.com>
mailto:tak...@fujitsu.com>> wrote:
Hi All,
I'm using the SSTable with Size Tired Compaction Strategy with
10 days gc grace period
ata the tombstone covers may possibly be in another SSTable. Only once
all SSTables that contain relevant data have been compacted with the SSTable
containing the tombstone can the tombstone be removed.
On 11 December 2017 at 01:08, tak...@fujitsu.com<mailto:tak...@fujitsu.com>
mailto:tak...@
?
Regards,
Takashima
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Monday, December 11, 2017 3:36 PM
To: user@cassandra.apache.org
Subject: Re: Tombstoned data seems to remain after compaction
Replies inline
On Dec 10, 2017, at 9:59 PM, "tak...@fujitsu.com<mailto:tak...@fujitsu.com>&q
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, December 12, 2017 2:35 AM
To: cassandra
Subject: Re: Tombstoned data seems to remain after compaction
Hello Takashima,
Answers inline.
On Sun, Dec 10, 2017 at 11:41 PM, tak...@fujitsu.com<mailto:tak...@fujitsu.com>
mail
o complete.
On 12 December 2017 at 07:44, tak...@fujitsu.com<mailto:tak...@fujitsu.com>
mailto:tak...@fujitsu.com>> wrote:
Hi Jeff, Kurt
Thanks again for your advice.
Within those valuable ideas you provide, I think of executing nodetool compact
because it is the most simplest way t
