git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tombstone


The most likely explanation is tombstones in files that won’t be collected as they potentially overlap data in other files with a lower timestamp (especially true if your partition key doesn’t change and you’re writing and deleting data within a partition)

-- 
Jeff Jirsa


> On Jun 19, 2018, at 3:28 AM, Abhishek Singh <abh2345x@xxxxxxxxx> wrote:
> 
> Hi all,
>            We using Cassandra for storing events which are time series based for batch processing once a particular batch based on hour is processed we delete the entries but we were left with almost 18% deletes marked as Tombstones.
>                  I ran compaction on the particular CF tombstone didn't come down.
>             Can anyone suggest what is the optimal tunning/recommended practice used for compaction strategy and GC_grace period with 100k entries and deletes every hour.
> 
> Warm Regards
> Abhishek Singh

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxxx




( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache-cassandra-users/msg06228.html on line 89
Call Stack
#TimeMemoryFunctionLocation
10.0006363400{main}( ).../msg06228.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache-cassandra-users/msg06228.html on line 89
Call Stack
#TimeMemoryFunctionLocation
10.0006363400{main}( ).../msg06228.html:0