There isnt anything wrong aside from your query is poorly thought out. On Fri, Jun 7, 2019 at 11:04 AM vishal patel <vishalpatel200...@outlook.com> wrote:
> Any one is looking my issue?? > > Get Outlook for Android<https://aka.ms/ghei36> > > ________________________________ > From: vishal patel > Sent: Thursday, June 6, 2019 5:15:15 PM > To: solr-user@lucene.apache.org > Subject: Re: Query takes a long time Solr 6.1.0 > > Thanks for your reply. > > > How much index data is on one server with 256GB of memory? What is the > > max heap size on the Solr instance? Is there only one Solr instance? > > One server(256GB RAM) has two below Solr instance and other application > also > 1) shards1 (80GB heap ,790GB Storage, 449GB Indexed data) > 2) replica of shard2 (80GB heap, 895GB Storage, 337GB Indexed data) > > The second server(256GB RAM and 1 TB storage) has two below Solr instance > and other application also > 1) shards2 (80GB heap, 790GB Storage, 338GB Indexed data) > 2) replica of shard1 (80GB heap, 895GB Storage, 448GB Indexed data) > > Both server memory and disk usage: > https://drive.google.com/drive/folders/11GoZy8C0i-qUGH-ranPD8PCoPWCxeS-5 > > Note: Average 40GB heap used normally in each Solr instance. when replica > gets down at that time disk IO are high and also GC pause time above 15 > seconds. We can not identify the exact issue of replica recovery OR down > from logs. due to the GC pause? OR due to disk IO high? OR due to > time-consuming query? OR due to heavy indexing? > > Regards, > Vishal > ________________________________ > From: Shawn Heisey <apa...@elyograg.org> > Sent: Wednesday, June 5, 2019 7:10 PM > To: solr-user@lucene.apache.org > Subject: Re: Query takes a long time Solr 6.1.0 > > On 6/5/2019 7:08 AM, vishal patel wrote: > > I have attached RAR file but not attached properly. Again attached txt > file. > > > > For 2 shards and 2 replicas, we have 2 servers and each has 256 GB ram > > and 1 TB storage. One shard and another shard replica in one server. > > You got lucky. Even text files usually don't make it to the list -- > yours did this time. Use a file sharing website in the future. > > That is a massive query. The primary reason that Lucene defaults to a > maxBooleanClauses value of 1024, which you are definitely exceeding > here, is that queries with that many clauses tend to be slow and consume > massive levels of resources. It might not be possible to improve the > query speed very much here if you cannot reduce the size of the query. > > Your query doesn't look like it is simple enough to replace with the > terms query parser, which has better performance than a boolean query > with thousands of "OR" clauses. > > How much index data is on one server with 256GB of memory? What is the > max heap size on the Solr instance? Is there only one Solr instance? > > The screenshot mentioned here will most likely relay all the info I am > looking for. Be sure the sort is correct: > > > https://wiki.apache.org/solr/SolrPerformanceProblems#Asking_for_help_on_a_memory.2Fperformance_issue > > You will not be able to successfully attach the screenshot to a message. > That will require a file sharing website. > > Thanks, > Shawn >
