[ 
https://issues.apache.org/jira/browse/HADOOP-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020094#comment-18020094
 ] 

ASF GitHub Bot commented on HADOOP-19469:
-----------------------------------------

github-actions[bot] closed pull request #7426: HADOOP-19469. Set Curator 
Connection Timeout.
URL: https://github.com/apache/hadoop/pull/7426




> Set Curator Connection Timeout
> ------------------------------
>
>                 Key: HADOOP-19469
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19469
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: hadoop-common
>    Affects Versions: 3.3.6, 3.5.0
>            Reporter: Xiao Yu
>            Priority: Minor
>              Labels: pull-request-available
>
> Curator 5.2.0 has a default "connection timeout" of 15s:
> [https://github.com/apache/curator/blob/apache-curator-5.2.0/curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java#L63]
> And it will throw a warning if the Zookeeper session timeout is less than the 
> Curator connection timeout:
> [https://github.com/apache/curator/blob/apache-curator-5.2.0/curator-client/src/main/java/org/apache/curator/CuratorZookeeperClient.java#L117-L120]
> The Hadoop default for ZK timeout is set to 10s:
> [https://github.com/apache/hadoop/blob/0dd9bf8/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/CommonConfigurationKeys.java#L414-L416]
> Which means without setting the "connection timeout" a default installation 
> will keep warning about the connection timeout for Curator being lower than 
> the requested session timeout. This sets both timeout values to override the 
> Curator default.
> Another option is to change the default Hadoop ZK timeout from 10s to 15s.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to