Re: Cassandra Compactions Speed increase

2017-09-15 Thread Jeff Jirsa
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

Re: Cassandra Compactions Speed increase

2017-09-15 Thread Ashish Pandey
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

Re: Cassandra Compactions Speed increase

2017-09-15 Thread Jeff Jirsa
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: > >

Cassandra Compactions Speed increase

2017-09-15 Thread Ashish Pandey
Hi All, We are using cassandra 3.9 and experiencing read latency issues. We are using LeveledCompactionStrategy after experiencing read latency issue with SizeTieredCompactionStrategy. For our use case, table keys are getting batch updated and batch delete of column values for keys. We almost

Re: Review request: CASSANDRA-13799

2017-09-15 Thread Jeff Jirsa
On 2017-09-06 00:58, Malcolm Taylor wrote: > Can someone please review my patch on CASSANDRA-13799 ? The issue fixes > several alerts raised by lgtm.com, which runs a deep analysis of the code > in trunk. Some of the alerts refer to clear bugs, while others are >

RE: question on the code formatter

2017-09-15 Thread Tyagi, Preetika
Thank you for the info! I tried it and it worked as expected. -Original Message- From: Murukesh Mohanan [mailto:murukesh.moha...@gmail.com] Sent: Thursday, September 14, 2017 11:10 PM To: dev@cassandra.apache.org Subject: Re: question on the code formatter The wiki seems to be

RE: Proposal: Closing old, unable-to-repro JIRAs

2017-09-15 Thread Tyagi, Preetika
+ 1 This is a good idea. -Original Message- From: beggles...@apple.com [mailto:beggles...@apple.com] Sent: Friday, September 15, 2017 8:29 AM To: dev@cassandra.apache.org Subject: Re: Proposal: Closing old, unable-to-repro JIRAs +1 to that On September 14, 2017 at 4:50:54 PM, Jeff

Re: Proposal: Closing old, unable-to-repro JIRAs

2017-09-15 Thread Blake Eggleston
+1 to that On September 14, 2017 at 4:50:54 PM, Jeff Jirsa (jji...@gmail.com) wrote: There's a number of JIRAs that are old - sometimes very old - that represent bugs that either don't exist in modern versions, or don't have sufficient information for us to repro, but the reporter has gone

materialise view creation taking too much time with 12 million data set

2017-09-15 Thread Pankaj Gajjar
Hi everyone, recently we are in big trouble while creating the materialise view(mv) on 12 million data set and then we wait for almost 72 hours. with same data model with half of data set 7 million it took only 10-15 mins to prepare same mv. please welcome any input on this.. -- Regards,

Re: question on the code formatter

2017-09-15 Thread Murukesh Mohanan
The wiki seems to be outdated. See https://github.com/apache/cassandra/blob/trunk/doc/source/development/ide.rst : > The project generated by the ant task ``generate-idea-files`` contains nearly everything > you need to debug Cassandra and execute unit tests. > > * Run/debug defaults for JUnit >