Re: Solr Cloud Autoscaling Basics

Any pointers here would be appreciated :) -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Solr Cloud Autoscaling Basics

Hi I have a master slave architecture setup currently. I'm evaluating SolrCloud. I've read through most of the documentation, but what I can't seem to find is the preferred way to autoscale the cluster. In the master slave architecture, we have a autoscaling policy (CPU based) configured on

Extremely Small Segments

Hi I am migrating from master slave to Solr Cloud but I'm running into problems with indexing. Cluster details: 8 machines of 64GB memory, each hosting 1 replica. 4 shards, 2 replica of each. Heap size is 16GB. Collection details: Total number of docs: ~250k (but only 50k are indexed right

Re: CMS GC - Old Generation collection never finishes (due to GC Allocation Failure?)

After none of the JVM configuration options helped witH GC, as Erick suggested I took a heap dump of one of the misbehaving slaves and analysis shows that fieldcache is using a large amount of the the total heap. Memory Analyzer output: One instance of

Re: CMS GC - Old Generation collection never finishes (due to GC Allocation Failure?)

Hi Shawn, thanks for the inputs. I have uploaded the gc logs of one of the slaves here: https://ufile.io/ecvag (should work till 18th Oct '18) I uploaded the logs to gceasy as well and it says that the problem is consecutive full GCs. According to the solution they have mentioned, increasing the

CMS GC - Old Generation collection never finishes (due to GC Allocation Failure?)

Hi I'm working with a Solr cluster with master-slave architecture. Master and slave config: ram: 120GB cores: 16 At any point there are between 10-20 slaves in the cluster, each serving ~2k requests per minute. Each slave houses two collections of approx 10G (~2.5mil docs) and 2G(10mil docs)

Replication on startup takes a long time

Hi We have setup a master-slave architecture for our Solr instance. Number of docs: 2 million Collection size: ~12GB when optimized Heap size: 40G Machine specs: 60G, 8 cores We are using Solr 6.2.1. Autocommit Configuration: 4 90 false

Re: CommitScheduler Thread blocked due to excessive number of Merging Threads

Hi Shawn Thanks for putting the settings in context. This definitely helps. Before I put these settings, I was doing a bit more digging, and wanted to really understand why the merging was so slow. Looking at the thread dump of Solr 6.6 and Solr 5.4, I found that in the merging process, the

Solr Commit Thread Blocked because of excessive number of merging threads

Hi My team has tasked me with upgrading Solr from the version we are using (5.4) to the latest stable version 6.6. I am stuck for a few days now on the indexing part. First I'll list the requirements, then all the configuration settings I have tried. So in total I'm indexing about 2.5million

Re: CommitScheduler Thread blocked due to excessive number of Merging Threads

So I did a little more digging around why the merging is taking so long, and it looks like merging postings is the culprit. On the 5.4 version, merging 500 docs is taking approximately 100 msec, while on the 6.6 version, it is taking more than 3000 msec. The difference seems to get worse when