It does not have to be query load - it can be one heavy query that cause memory consumption (heavy faceting, deep paging,…) and after that GC jumps in. Maybe you could start with log and see if there are queries that have large QTime,
Emir > On 22 Sep 2017, at 12:00, shamik <sham...@gmail.com> wrote: > > All the tuning and scaling down of memory seemed to be stable for a couple of > days but then came down due to a huge spike in CPU usage, contributed by G1 > Old Generation GC. I'm really puzzled why the instances are suddenly > behaving like this. It's not that a sudden surge of load contributed to > this, query and indexing load seemed to be comparable with the previous time > frame. Just wondering if the hardware itself is not adequate enough for 6.6. > The instances are all running on 8 CPU / 30gb m3.2xlarge EC2 instances. > > Does anyone ever face issues similar to this? > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
