Normally whenever I see a 503, that means the Solr Cloud has one of its
shards down, i.e. there isn't a full collection available.
You can see them at index time if you have lost connection to zookeeper but
searches should be ok.
If you see them on searches, it (in my experience) means the collection
doesn't have all the necessary servers up.
On 14 May 2013 14:16, Furkan KAMACI <furkankam...@gmail.com> wrote:
> When I check my SolrCloud nodes' log files (Solr 4.2.1) I get see that line
> at all of them:
>
> INFO: [collection1] webapp=/solr path=/admin/file/
> params={file=admin-extra.html&_=1368535805558} status=0 QTime=5
> May 14, 2013 3:50:27 PM org.apache.solr.core.SolrCore execute
> INFO: [collection1] webapp=/solr path=/admin/luke
> params={numTerms=0&_=1368535805536&show=index&wt=json} status=0 QTime=1
> May 14, 2013 3:50:27 PM org.apache.solr.core.SolrCore execute
> INFO: [collection1] webapp=/solr path=/admin/ping
> params={action=status&_=1368535805560&wt=json} *status=503* QTime=0
> May 14, 2013 3:50:32 PM org.apache.solr.core.SolrCore execute
> INFO: [collection1] webapp=/solr path=/replication
> params={slave=false&command=details&wt=javabin&qt=/replication&version=2}
> status=0 QTime=0
>
> /admin/ping listed as INFO however has a status 503? Does that status is
> HTTP status and what it means for me?
>
