The Solr logs themselves may give you a better error message. Best, Erick
On Tue, Apr 12, 2016 at 6:37 AM, Robert Brown <r...@intelcompute.com> wrote: > Hi, > > My collection had issues earlier, 1 shard showed as Down, the other only > replica was Gone. > > Both were actually still up and running, no disk or CPU issues. > > This occurred during updates. > > The server since recovered after a reboot. > > Upon trying to update the index again, I'm now getting constant Bad > Requests. > > Does anyone know what the issue could be, and/or how to resolve it? > > org.apache.solr.common.SolrException: Bad Request > > request: > http://hostname:8983/solr/de_shard1_replica1/update?update.distrib=TOLEADER&distrib.from=http%3A%2F%2Fhostname%3A8983%2Fsolr%2Fde_shard2_replica2%2F&wt=javabin&version=2 > at > org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.sendUpdateStream(ConcurrentUpdateSolrClient.java:287) > at > org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:160) > at > org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$1.run(ExecutorUtil.java:232) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > I also occasionaly get "Exception writing document id be-de-109513-307573357 > to the index; possible analysis error.' which was the first bunch of errors > I saw. > > Thanks, > Rob > >
