You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Benson Margulies (Created) (JIRA)" <ji...@apache.org> on 2012/04/09 18:17:19 UTC

[jira] [Created] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

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
            Reporter: Benson Margulies


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>
{noformat} 

doesn't have enough stuff in it. Would it be reasonable to ask for a better diagnosis?




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Issue Comment Edited] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Benson Margulies (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249974#comment-13249974 ] 

Benson Margulies edited comment on SOLR-3342 at 4/9/12 5:17 PM:
----------------------------------------------------------------

My diagnosis was wrong. I had no uniqueKey in my schema. I humbly submit that this should be diagnosed by refusing to start the cluster.

                
      was (Author: bmargulies):
    My diagnosis was wrong. My docs have no value in the unique Id field. I humbly submit that if PeerClient can't derive an id in getIndexedId, it should log or throw something specific, not just leave it null.

                  
> 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
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Commented] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Benson Margulies (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249925#comment-13249925 ] 

Benson Margulies commented on SOLR-3342:
----------------------------------------

I've answered my own question: DistributedUpdateProcessorFactory. Where could I edit a wiki to save someone else the trouble?

                
> 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
>            Reporter: Benson Margulies
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Updated] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Benson Margulies (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated SOLR-3342:
-----------------------------------

    Comment: was deleted

(was: I've answered my own question: DistributedUpdateProcessorFactory. Where could I edit a wiki to save someone else the trouble?
)
    
> 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
>            Reporter: Benson Margulies
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Commented] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Mark Miller (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249940#comment-13249940 ] 

Mark Miller commented on SOLR-3342:
-----------------------------------

bq. Would it be reasonable to ask for a better diagnosis?

Yup.
                
> 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
>            Reporter: Benson Margulies
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Commented] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Mark Miller (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249943#comment-13249943 ] 

Mark Miller commented on SOLR-3342:
-----------------------------------

For your issue thought, you are missing DistributedUpdateProcessorFactory - it should come before the RunUpdate processor factory.
                
> 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
>            Reporter: Benson Margulies
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Commented] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Benson Margulies (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249974#comment-13249974 ] 

Benson Margulies commented on SOLR-3342:
----------------------------------------

My diagnosis was wrong. My docs have no value in the unique Id field. I humbly submit that if PeerClient can't derive an id in getIndexedId, it should log or throw something specific, not just leave it null.

                
> 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
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Updated] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Benson Margulies (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated SOLR-3342:
-----------------------------------

    Description: 
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?



  was:
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>
{noformat} 

doesn't have enough stuff in it. Would it be reasonable to ask for a better diagnosis?




    
> 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
>            Reporter: Benson Margulies
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Assigned] (SOLR-3342) Diagnosis of lacking 'indexedId' seems to be lacking

Posted by "Mark Miller (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller reassigned SOLR-3342:
---------------------------------

    Assignee: Mark Miller
    
> 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
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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