On 5/16/2013 9:18 AM, Furkan KAMACI wrote:
It is a single node, started as standalone. I have just started a Solr
instance without SolrCloud.
2013/5/16 Yago Riveiro <yago.rive...@gmail.com>
Probably one or more shards of your collection are not available at ping
operation time and the server returns the 503 code
--
Yago Riveiro
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Thursday, May 16, 2013 at 3:58 PM, Furkan KAMACI wrote:
I have made some little changes at example folder of Solr 4.2.1 When I
start up it just with:
java -jar start.jar
I get that status:
INFO: [collection1] webapp=/solr path=/admin/ping
params={action=status&_=1368715926563&wt=json} status=503 QTime=0
When a ping request failed, older Solr versions logged a huge java
stacktrace and an error, and most of the time that information was not
very helpful.
Can you share your ping handler definition? I would guess that the
query in your ping handler is failing, or that you have a
healthcheckFile configured and it doesn't exist, so you would need to
enable it.
http://server:port/solr/corename/admin/ping?action=enable
Here's how one of my ping handlers is set up:
<requestHandler name="/admin/ping" class="solr.PingRequestHandler">
<lst name="invariants">
<str name="qt">/lbcheck</str>
<str name="q">*:*</str>
<str name="df">Body</str>
</lst>
<lst name="defaults">
<str name="echoParams">all</str>
</lst>
<str name="healthcheckFile">server-enabled.txt</str>
</requestHandler>
When the ping handler is called, it sends a query for all docs to a
search handler named /lbcheck (load balancer check), with a default
field of Body. The healthcheckFile is relative to dataDir. The enable
action creates this file, and the disable action deletes the file.
Thanks,
Shawn
