[ 
https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandre Rafalovitch closed SOLR-3342.
---------------------------------------
    Resolution: Not A Problem

Old discussion that turned out to be not a bug. If error reporting still needs 
to be improved, I suggest a new case with the latest Solr and updated suggested 
message.

> Diagnosis of lacking 'indexedId' seems to be lacking
> ----------------------------------------------------
>
>                 Key: SOLR-3342
>                 URL: https://issues.apache.org/jira/browse/SOLR-3342
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0-ALPHA
>            Reporter: Benson Margulies
>            Assignee: Mark Miller
>
> I tried to use CloudSolrServer via code that works fine with an ordinary, 
> non-sharded deployment.
> I got this backtrace on the client:
> {noformat}
> Caused by: org.apache.solr.client.solrj.SolrServerException: No live 
> SolrServers available to handle this 
> request:[http://tinfoilhat.local:9170/solr, 
> http://tinfoilhat.local:9169/solr, http://tinfoilhat.local:9167/solr]
>       at 
> org.apache.solr.client.solrj.impl.LBHttpSolrServer.request(LBHttpSolrServer.java:326)
>       at 
> org.apache.solr.client.solrj.impl.CloudSolrServer.request(CloudSolrServer.java:188)
>       at 
> org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:104)
>       at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:122)
>       at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:107)
> {noformat}
> Which was in turn caused by:
> {noformat}
> Apr 9, 2012 12:06:13 PM org.apache.solr.common.SolrException log
> SEVERE: null:java.lang.NullPointerException
>       at 
> org.apache.solr.update.processor.DistributedUpdateProcessor.hash(DistributedUpdateProcessor.java:855)
>       at 
> org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:252)
>       at 
> org.apache.solr.update.processor.LogUpdateProcessor.processAdd(LogUpdateProcessorFactory.java:97)
>       at org.apache.solr.handler.XMLLoader.processUpdate(XMLLoader.java:135)
> ...
> {noformat}
> Which was in turn caused by the fact that the AddUpdateCommand object has 
> nothing in the indexedId.
> I think that this must be caused by:
> {noformat}
>     <updateRequestProcessorChain name="RNI">
>      <!-- some day, add parameters when we have some -->
>      <processor 
> class="com.basistech.rni.solr.NameIndexingUpdateRequestProcessorFactory"/>
>      <processor class="solr.LogUpdateProcessorFactory" />
>      <processor class="solr.RunUpdateProcessorFactory" />
>    </updateRequestProcessorChain>
>   <requestHandler name="/update" 
>                   class="solr.XmlUpdateRequestHandler">
>     <lst name="defaults">
>       <str name="update.chain">RNI</str>
>     </lst>
>     </requestHandler>
> {noformat} 
> doesn't have enough stuff in it. Would it be reasonable to ask for a better 
> diagnosis?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to