Re: RangeAwareCompaction for manual token management

2018-07-22 Thread Marcus Eriksson
It should work fine with num_tokens: 1 Without vnodes it also flushes to per-range sstables (if you have RF=3 you will "always" get 3 sstables after flush), while with vnodes it groups the ranges and flushes a full disk, so if you have a single data_file_directories you get only one sstable, then

Re: RangeAwareCompaction for manual token management

2018-07-19 Thread kurt greaves
I've had similar thoughts in the past about RACS and manual tokens. I think it would be a good idea to be able to split it based on some configurable factor other than vnodes. I think Marcus may have already addressed this to some extent as well but if not it's theoretically possible. On 20 July

RangeAwareCompaction for manual token management

2018-07-19 Thread Carl Mueller
I don't want to comment on the 10540 ticket since it seems very well focused on vnode-aligned sstable partitioning and compaction. I'm pretty excited about that ticket. RACS should enable: - smaller scale LCS, more constrained I/O consumption - less sstables to hit in read path -