We ran for months with the same highly tuned setup on 2.1 and once we switched to 3.0.9 the performance with the same configuration was crap. Leveled compaction but a bit more nodes. There are differences in how 2.1 and 3.0 work so I guess you need to revisit your cassandra.yaml and os settings. Next to everything Jeff mentioned, is there any reason you have data on all nodes and use QUORUM? Also, is there any reason you are not using G1 with 3.0?
On Thu, Feb 2, 2017 at 6:28 AM, Jeff Jirsa <jji...@gmail.com> wrote: > Can you quantify "major"? > > Latency or throughput? > GC pauses? > What did you see before? What do you see now? > Do you have a stack dump? > > > -- > Jeff Jirsa > > > > On Feb 1, 2017, at 4:23 PM, Shashank Joshi <shashank.jo...@ericsson.com> > wrote: > > > > We are seeing major performance issues with about 100 GB of data in > 3.0.9-E001. The exact same app runs very well in 2.1. > > > > > > > > It feels to us like something is wrong with our configuration because of > the severity of the issues. Thanks in advance for any recommendations or > suggestions. > > > > > > > > Details: > > > > Size of data: 100 GB+ all in one table, with a simple schema, couple of > bigints and a double > > > > Cluster: 3 nodes with RF of 3 > > > > Client: App uses read and write CL of QUORUM and we have a lots of > timeouts due to inability to reach quorum > > > > Compaction: Leveled > > > > Nature of data usage: No updates/deletes, High reads, relatively low > writes > > > > > > > > > > > > JVM: > > > > Using CMS GC and around 8 GB of max heap > > >
