You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2017/12/19 03:30:03 UTC

[jira] [Created] (SOLR-11776) HttpSolrClient should handle SocketException:broken pipe

Cao Manh Dat created SOLR-11776:
-----------------------------------

             Summary: HttpSolrClient should handle SocketException:broken pipe
                 Key: SOLR-11776
                 URL: https://issues.apache.org/jira/browse/SOLR-11776
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Cao Manh Dat


There is a case when leader sends an update to replica but met {{SocketException: broken pipe}} ( HttpPartitionTest ), the leader treat this exception as others SocketException and put replica into LIR mode. But this exception means an existing connection between leader and replica is closed on one side. I think we should handle this exception in a different way ( ex: reconnect ) so leader won't blindly put replica into LIR even when the connection between leader and replica is healthy.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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