You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Joshi, Shital" <Sh...@gs.com> on 2014/03/14 22:54:00 UTC

solr4 log message

I see lots of messages like this in solr4 logs. What is it for?


INFO  - 2014-03-14 16:42:47.098; org.apache.solr.core.SolrCore; [collection1] webapp=/solr path=/select params={NOW=1394829767088&shard.url=us123.abc.com:8983/solr/collection1/|us234.abc.com:8983/solr/collection1/&fl=q_idn_s,score&df=text&start=0&distrib=false&wt=javabin&isShard=true&fsv=true&version=2&rows=10} hits=0 status=0 QTime=0

INFO  - 2014-03-14 16:42:47.163; org.apache.solr.core.SolrCore; [collection1] webapp=/solr path=/select  params={NOW=1394829767152&shard.url=us123.abc.com:8983/solr/collection1/|us234.abc.com:8983/solr/collection1/&fl=q_idn_s,score&df=text&start=0&distrib=false&wt=javabin&isShard=true&fsv=true&version=2&rows=10} hits=0 status=0 QTime=0


Thanks!


Re: solr4 log message

Posted by Shawn Heisey <so...@elyograg.org>.
On 3/14/2014 3:54 PM, Joshi, Shital wrote:
> I see lots of messages like this in solr4 logs. What is it for?
>
>
> INFO  - 2014-03-14 16:42:47.098; org.apache.solr.core.SolrCore; [collection1] webapp=/solr path=/select params={NOW=1394829767088&shard.url=us123.abc.com:8983/solr/collection1/|us234.abc.com:8983/solr/collection1/&fl=q_idn_s,score&df=text&start=0&distrib=false&wt=javabin&isShard=true&fsv=true&version=2&rows=10} hits=0 status=0 QTime=0
>
> INFO  - 2014-03-14 16:42:47.163; org.apache.solr.core.SolrCore; [collection1] webapp=/solr path=/select  params={NOW=1394829767152&shard.url=us123.abc.com:8983/solr/collection1/|us234.abc.com:8983/solr/collection1/&fl=q_idn_s,score&df=text&start=0&distrib=false&wt=javabin&isShard=true&fsv=true&version=2&rows=10} hits=0 status=0 QTime=0

Something sent Solr a query.  To find out what's sending the query, 
you'd need to either get a sniffer trace or look at the log for the 
servlet container that is running Solr.

It looks like it might be part of a SolrCloud query, so if you have more 
than one server, the actual query might be hitting one of the others.

Thanks,
Shawn