Any pointers on what I should be looking for in our application that would be stopping the deletion of tombstones?
Thanks, Ross On 26 March 2012 16:27, Viktor Jevdokimov <viktor.jevdoki...@adform.com>wrote: > Upon read from S1 & S6 rows are merged, T3 timestamp wins. > T1 will be deleted upon S1 compaction with S6 or manual cleanup. > We're running major compactions nightly, a lot of inserts per day with > TTL, some with deletes from app - no problems with tombstones. > > > Best regards/ Pagarbiai > > Viktor Jevdokimov > Senior Developer > > Email: viktor.jevdoki...@adform.com > Phone: +370 5 212 3063 > Fax: +370 5 261 0453 > > J. Jasinskio 16C, > LT-01112 Vilnius, > Lithuania > > > > Disclaimer: The information contained in this message and attachments is > intended solely for the attention and use of the named addressee and may be > confidential. If you are not the intended recipient, you are reminded that > the information remains the property of the sender. You must not use, > disclose, distribute, copy, print or rely on this e-mail. If you have > received this message in error, please contact the sender immediately and > irrevocably delete this message and any copies.-----Original Message----- > From: Radim Kolar [mailto:h...@filez.com] > Sent: Sunday, March 25, 2012 13:20 > To: user@cassandra.apache.org > Subject: Re: tombstones problem with 1.0.8 > > Scenario 4 > T1 write column > T2 Flush memtable to S1 > T3 del row > T4 flush memtable to S5 > T5 tomstone S5 expires > T6 S5 is compacted but not with S1 > > Result? >
