[
https://issues.apache.org/jira/browse/SOLR-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107250#comment-14107250
]
Mark Miller commented on SOLR-6405:
-----------------------------------
bq. Is that too much?
I'm much more worried about doing too little than too much, that is why it was
done that way. Perhaps the padding could be brought down (it was probably
brought up to combat a sign of this bug - it was 1200 initially I think), but I
think we want to error on the long wait side.
bq. // 1500 ms over for padding
Hmm, actually 500 over was right. It's mean to be a second, so anything over
1000 is the padding.
> ZooKeeper calls can easily not be retried enough on ConnectionLoss.
> -------------------------------------------------------------------
>
> Key: SOLR-6405
> URL: https://issues.apache.org/jira/browse/SOLR-6405
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 5.0, 4.10
>
> Attachments: SOLR-6405.patch
>
>
> The current design requires that we are sure we retry on connection loss
> until session expiration.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
