Thanks!, I will try out changing concurrent compactors and provide more
info for further help after trying. I agree that I haven't provided any
info to get help :).
Performance is disk bound (I think the reason is L0 use STCS), host stats
doesn't show any significant CPU and Load. Read latency is i
Check your settings for concurrent compactors (in your yaml) and throughput
(can check and set with nodetool) - both of those can be adjusted
Beyond that you need to give a bit more info to help us help you - are you CPU
bound, disk bound, is the read load the limiter or is compaction? We need
I haven't throttled cassandra compactions. My assumption is that because we
are running lot of batch jobs which can updates or delete partition key,
number of compactions are too many to finish in time which i see in
nodetool compactionstats pending tasks.
Multiple Batch write (and delete) of part
Do you have compaction throttled now?
What exactly takes 6-8 hours?
Are you writing all the keys at one time, then reading, then deleting them all,
or is it a constant stream of writes and reads?
--
Jeff Jirsa
> On Sep 15, 2017, at 8:40 PM, Ashish Pandey wrote:
>
> Hi All,
>
> We are usin
