the 10 days is actually configurable... look into gc_grace. Basically, you always need to run repair once per/gc_grace period. You won't see empty/deleted rows go away until they're compacted away.
On Mon, Oct 1, 2012 at 6:32 PM, Hiller, Dean <dean.hil...@nrel.gov> wrote: > I know there is a 10 day limit if you have a node out of the cluster where > you better be running read-repair or you end up with forgotten deletes, but > what about on a clean cluster with all nodes always available? Shouldn't the > deletes eventually take place or does one have to keep running read-repair > manually all the time(god, I hope not as that should be automated for > deletes). > > I am seeing the empty rows in the CLI right now like so…(and would prefer > they go away on their own)… > > RowKey: post:10079376916:b2:4045302966737879216 > ------------------- > RowKey: post:10079386137:b2:3120637961487430473 > ------------------- > RowKey: post:10079377944:b2:5118918738052923761 > ------------------- > RowKey: post:10079378212:b2:1449128414219430571 > ------------------- > RowKey: post:10079386010:b2:8567843818586569179 > > If not, someone has to already have an automated project for this, anyone > know of one?? > > Thanks, > Dean > -- Aaron Turner http://synfin.net/ Twitter: @synfinatic http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin "carpe diem quam minimum credula postero"
