Look for the line like this in your log with the search matching the
body. Maybe put a nonsense string and look for that. This should tell
you what the Solr-side search looks like.
The thing that worries me here is: rows=107178 - that's most probably
what's blowing up Solr. You should be paging, not getting everything.
And that number being like that, it may mean your client makes two
requests, once to get the result count and once to get the rows
themselves. It's the second request that is most probably blowing up.
Once you get the request, you should be able to tell what fields are
being searched and check those fields in schema.xml for field type and
then field type's definition. Which is what I asked for in the
previous email.
Regards,
Alex.
On 24 February 2015 at 11:55, Kevin Laurie <superinterstel...@gmail.com> wrote:
> 155092 [qtp433527567-13] INFO org.apache.solr.core.SolrCore ?
> [collection1] webapp=/solr path=/select
> params={sort=uid+asc&fl=uid,score&q=subject:"price"&fq=%2Bbox:ac553604f7314b54e62300003555fc1a+%2Buser:"u...@domain.net"&rows=107178}
> hits=1237 status=0 QTime=1918
----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
