[
https://issues.apache.org/jira/browse/SOLR-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-3647:
-------------------------------
This was actually a fairly bad bug as brought up on the user list a week or two
back - the std zk client does not deal with connection loss well, but worse,
once it's had a connection expiration, you have to make a new client - you
cannot use the old one. So if the distrib queue zk client ever gets expired, it
will continually hit expiration exceptions as you try to use it again - so no
nodes can publish states (other issues too, but thats a big one). This can put
in in an infinite recovery loop.
> DistrubtedQueue should use our Solr zk client rather than the std zk client.
> ----------------------------------------------------------------------------
>
> Key: SOLR-3647
> URL: https://issues.apache.org/jira/browse/SOLR-3647
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0, 5.0
>
>
> This will let us easily do retries on connection loss.
--
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: [email protected]
For additional commands, e-mail: [email protected]
