You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/09 09:31:00 UTC
[jira] [Commented] (CURATOR-475) Cannot effectively set
connectionTimeout < 1000ms
[ https://issues.apache.org/jira/browse/CURATOR-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574556#comment-16574556 ]
ASF GitHub Bot commented on CURATOR-475:
----------------------------------------
Github user matobet commented on the issue:
https://github.com/apache/curator/pull/274
@Randgalt thank you for the quick response. I created https://issues.apache.org/jira/browse/CURATOR-475 for this. Should I discard this PR and make a new one from a branch named CURATOR-475 now or we can somehow links this existing PR with the created JIRA?
> Cannot effectively set connectionTimeout < 1000ms
> -------------------------------------------------
>
> Key: CURATOR-475
> URL: https://issues.apache.org/jira/browse/CURATOR-475
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Reporter: Martin Betak
> Priority: Major
>
> Regardless of the value set in {{connectionTimeoutMs}} the
> {{CuratorZookeeperClient#internalBlockUntilConnectedOrTimedOut}} method does
> the initial wait with value of 1 second, effectively making settings lower than
> this value ineffective. A simple change that would change the {{1 second}} to {{min(remainingWaitTime, 1 second)}} would solve the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)