[ https://issues.apache.org/jira/browse/SOLR-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107242#comment-14107242 ]
Jessica Cheng Mallet commented on SOLR-6405: -------------------------------------------- {quote} but not so long as we are waiting for no reason and tying up threads {quote} This is actually the other thing that I was worried about. With the padding being on a multiplier, for the default 15s timeout, we're already doing 7.5s of total extra sleep (1.5+3+4.5+6+7.5=22.5). Is that too much? With your change of the comment "// 1500 ms over for padding", did you actually mean to do something like (attemptCount + 1) * 1000 + retryDelay? > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org