Hello Shawn,
We found that it is unrelated to the group queries instead more
related to the empty queries. Do you happen to know what could cause empty
queries like the following from SOLRJ ? I can generate similar query via
curl hitting the select handler like - http://server:port/solr/select
server.log_2013-04-26T05-02-22:[#|2013-04-26T04:33:39.065-0400|INFO|sun-appserver2.1.1|org.apache.solr.core.SolrCore|_ThreadID=38;_ThreadName=httpSSLWorkerTh
read-9001-11;|[xxxcore] webapp=/solr path=/select params={} hits=24099
status=0 QTime=19 |#]
What we are seeing is a huge number of these empty queries. Once this
happens I have observed 2 things
1. even if I query from admin console, irrespective of the query, I get
same results as if its a cached page of *:* query. i.e. I cannot see the
query I entered in the server log, the query doesn't even come to the
server but I get same results as *:*
2. If I query via solrj no results are returned.
This has been driving me nuts for almost a week. Any help is greatly
appreciated.
Thanks
Ravi Kiran Bhaskar
On Sat, Apr 20, 2013 at 10:33 PM, Ravi Solr <ravis...@gmail.com> wrote:
> Thanks for your advise Shawn. I have created a JIRA issue SOLR-4743.
>
>
> On Sat, Apr 20, 2013 at 4:32 PM, Shawn Heisey <s...@elyograg.org> wrote:
>
>> On 4/20/2013 9:08 AM, Ravi Solr wrote:
>> > Thanks you very much for responding Shawn. I never use IE, I use
>> firefox.
>> > These are brand new servers and I don't think I am mixing versions. What
>> > made you think I was using the 1.4.1 ?? You are correct in saying that
>> the
>> > server is throwing HTML response since a group query has been failing
>> with
>> > SEVERE error following which the entire instance behaves weirdly until
>> we
>> > restart.
>> >
>> > Its surprising that group query error handling has such glaring issue.
>> If
>> > you specify group=true but don't specify group.query or group.field SOLR
>> > throws a SEVERE exception following which we see the empty queries and
>> > finally no responses via solrj and admin console gives numFound always
>> > equal to total number of docs in index . Looks like the searcher goes
>> for a
>> > spin once it encounters the exception. Such situation should have been
>> > gracefully handled
>>
>> Ah, so what's happening is that after an invalid grouping query, Solr is
>> unstable and stops working right. You should file an issue in Jira,
>> giving as much detail as you can. My last message was almost completely
>> wrong.
>>
>> You are right that it should be gracefully handled, and obviously it is
>> not. For the 3.x Solr versions, grouping did not exist before 3.6. It
>> is a major 4.x feature that was backported. Sometimes such major
>> features depend on significant changes that have not happened on older
>> versions, leading to problems like this. Unfortunately, you could wait
>> quite a while for a fix on 3.6, where active development has stopped.
>>
>> I have no personal experience with grouping, but I just tried the
>> problematic query (adding "&group=true" to one that works) on 4.2.1. It
>> doesn't throw an error, I just get no results. When I follow it with a
>> regular query, everything works perfectly. Would you be able to upgrade
>> to 4.2.1? That's not a trivial thing to do, so hopefully you are
>> already working on upgrading.
>>
>> Thanks,
>> Shawn
>>
>>
>
