Jason,
Not yet.This issue was on the back burner for a few daysHowever we
still need to figure out what could be a potential solution to it.
The setup is basic one - with one node / no shards or replicas
2 cores
When I run the query adding debug=timing to raw query parameters it just
hangs
Hey Abhijit,
The information you provided isn't really enough for anyone else on
the mailing list to debug the problem. If you'd like help, please
provide some more information.
Good places to start would be: what is the query, what does Solr tell
you when you add a "debug=timing" parameter to
Hello,
I am seeing a performance issue in querying in one of the SOLR servers -
instance version 5.4.1.
Total number of documents indexed are 20K plus.
Data returned for this particular query is just as less as 22 documents
however it takes almost 2 minutes to get the results back.
Is there a
Thanks Jack for your response.
The users of our application can enter a list of ids which the UI caps at
50k. All the ids are valid and match documents. We do faceting, grouping
etc. on the result set of up to 50k documents.
I checked and found that the query is not very resource intensive. It is
A single query with tens of thousands of terms is very clearly a misuse of
Solr. If it happens to work at all, consider yourself lucky. Are you using
a standard Solr query parser or the terms query parser that lets you write
a raw list of terms to OR.
Are your nodes CPU-bound or I/O-bound during
Hi,
I have a field f which is defined as follows.
Solr-5.2.1 is used. The index is spread across 12 shards (no replica) and
the index size on each node is around 100 GB.
When I search for 50 thousand values (ORed) in the field f it takes almost
around 45 to 55 seconds.
Per my understanding it
