[jira] [Closed] (SOLR-5938) ConcurrentUpdateSolrServer don't parser the response while response status code isn't 200

["Cassandra Targett (JIRA)" <ji...@apache.org>]

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

Cassandra Targett closed SOLR-5938.
-----------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 6.0)
                       (was: 4.9)

> ConcurrentUpdateSolrServer don't parser the response while response status code isn't 200
> -----------------------------------------------------------------------------------------
>
>                 Key: SOLR-5938
>                 URL: https://issues.apache.org/jira/browse/SOLR-5938
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.6.1
>         Environment: one cloud has two server, one shard, one leader one replica, send the index into replica server, replica server forward leader server.
>            Reporter: Raintung Li
>              Labels: SolrCloud, difficulty-easy, impact-low, solrj
>         Attachments: SOLR-5938.txt
>
>
> ConcurrentUpdateSolrServer only give back the error that don't parser the response body, you can't get the error reason from remote server. 
> EX.
> You send the index request to one solr server, this server forward the other leader server. forward case invoke the ConcurrentUpdateSolrServer.java, you can't get the right error message only check it in the leader server if happen error. Actually leader server had sent the error message to the forwarding server.



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

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