If you make all as 10gb each, they will compact immediately into same size
The idea is actually to trigger the compaction so the tombstones will be
removed. That's the whole purpose of the split. and if the split sstable
has lots of tombstones, it'll be compacted to a much smaller size.
Also, you can always play with the compaction threshold to suit your needs.
<http://www.facebook.com/LivePersonInc> We Create Meaningful Connections
On Wed, May 17, 2017 at 8:23 PM, Nitan Kainth <ni...@bamlabs.com> wrote:
> Right, but realistically that is what happens with SizeTiered. Another
> option is to split the tables in proportion size NOT same size. Like 100 GB
> into 50, 25, 12,13. If you make all as 10gb each, they will compact
> immediately into same size again. Motive is to get rid of duplicates which
> exist on smaller tables outside this one big table (as per my understanding
> from your email).
> IOn May 17, 2017, at 12:20 PM, Hannu Kröger <hkro...@gmail.com> wrote:
> Basically meaning that if you run major compaction (=nodetool compact),
> you will end up with even bigger file and that is likely to never get
> compacted without running major compaction again. And therefore not
> recommended for production system.
> On 17 May 2017, at 19:46, Nitan Kainth <ni...@bamlabs.com> wrote:
> You can try running major compaction to get rid of duplicate data and
> deleted data. But will be the routine for future.
> On May 17, 2017, at 10:23 AM, Jan Kesten <j.kes...@enercast.de> wrote:
> me patt
This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of the
addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.