Hi everyone, As per suggestions in previous post (by Erick and Shawn) we did following changes.
OLD <filterCache class="solr.CaffeineCache" size="32768" initialSize="6000" autowarmCount="6000"/> <queryResultCache class="solr.CaffeineCache" size="25600" initialSize="6000" autowarmCount="0"/> <documentCache class="solr.CaffeineCache" size="32768" initialSize="6144" autowarmCount="0"/> NEW <filterCache class="solr.CaffeineCache" size="8192" initialSize="512" autowarmCount="512"/> <queryResultCache class="solr.CaffeineCache" size="8192" initialSize="3000" autowarmCount="0"/> <documentCache class="solr.CaffeineCache" size="8192" initialSize="3072" autowarmCount="0"/> *Reduced JVM heap size from 30GB to 26GB* GC setting: GC_TUNE=" \ -XX:+UseG1GC \ -XX:+PerfDisableSharedMem \ -XX:+ParallelRefProcEnabled \ -XX:G1HeapRegionSize=8m \ -XX:MaxGCPauseMillis=150 \ -XX:InitiatingHeapOccupancyPercent=60 \ -XX:+UseLargePages \ -XX:+AggressiveOpts \ " Solr Collection details: (running in solrCloud mode) It has 6 shards, and each shard has only one replica (which is also a leader) and replica type is NRT Each shard Index size: 11 GB avg size/doc: 1.0Kb We are running indexing on this collection: *Indexing rate: 2.4 million per hour* *The query rate is zero. Still commit with opensearcher=true is taking 25 to 28 minutes.* Is this because of heavy indexing? Also, with an increase in the number of documents in collection commit time is increasing. This is not our production system. In the prod system generally, our indexing rate is 5k/hour. Is it expected to have such high commit time with the above indexing rate? -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html