access patterns, I’m pretty
> confident that things will go well. I just wish that confidence were backed
> up by experience rather than conjecture.
>
> Robert
>
> From: Anthony Grasso
> Reply-To:
> Date: Friday, January 10, 2014 at 7:12 PM
> To:
> Subject: Re: Gotch
, I¹m pretty confident
that things will go well. I just wish that confidence were backed up by
experience rather than conjecture.
Robert
From: Anthony Grasso
Reply-To:
Date: Friday, January 10, 2014 at 7:12 PM
To:
Subject: Re: Gotchas when creating a lot of tombstones
Hi Robert,
It
Hi Robert,
It sounds like you have done a fair bit investigating and testing already.
Have you considered using a time based data model to avoid doing deletions
in the database?
Regards,
Anthony
On Thu, Jan 9, 2014 at 1:26 PM, sankalp kohli wrote:
> With Level compaction, you will have some da
With Level compaction, you will have some data which could not be reclaimed
with gc grace=0 because it has not compacted yet. For this you might want
to look at tombstone_threshold
On Wed, Jan 8, 2014 at 10:31 AM, Tyler Hobbs wrote:
>
> On Wed, Jan 1, 2014 at 7:53 AM, Robert Wille wrote:
>
>>
On Wed, Jan 1, 2014 at 7:53 AM, Robert Wille wrote:
>
> Also, for this application, it would be quite reasonable to set gc grace
> seconds to 0 for these tables. Zombie data wouldn’t really be a problem.
> The background process that cleans up orphaned browse structures would
> simply re-delete a
I¹ve seen a number of people on this forum that have run into a variety of
issues when creating a lot of tombstones. This makes me concerned about an
application that I¹m writing. It works great on my test server, but I¹m
concerned about what will happen when I move my production server to it. I¹m
