Re: How to minimize side effects induced by tombstones when using deletion?

2017-08-01 Thread kurt greaves
> Also, if we repaired once successfully, will the next repair process take a more reasonable time? Depends on if there was a lot of inconsistent data to repair in the first place. Also full repairs or incremental? Repairs are complicated and tricky to get working efficiently. If you're using

Re: How to minimize side effects induced by tombstones when using deletion?

2017-08-01 Thread Jing Meng
Thanks, we'll try delete range of rows as it seems to fit our scenario. One more question, as you mentioned "repair often" - and we have seen that several times, the official doc, representations, blogs, etc. But when we repair a column family sized to terabytes on a cluster with ~30 nodes, it

Re: How to minimize side effects induced by tombstones when using deletion?

2017-08-01 Thread Jeff Jirsa
Delete using as few tombstones as possible (deleting the whole partition is better than deleting a row; deleting a range of rows is better than deleting many rows in a range). Repair often and lower gc_grace_seconds so the tombstones can be collected more frequently -- Jeff Jirsa > On Jul