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

Hudson commented on HDFS-9914:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13147 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13147/])
HDFS-9914. Fix configurable WebhDFS connect/read timeout. Contributed by (arp: 
rev cd2a1dd0630e99e6696a9f0e8dc972604d38046a)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/web/WebHdfsFileSystem.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/web/URLConnectionFactory.java


> Fix configurable WebhDFS connect/read timeout
> ---------------------------------------------
>
>                 Key: HDFS-9914
>                 URL: https://issues.apache.org/jira/browse/HDFS-9914
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client, webhdfs
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Blocker
>             Fix For: 2.9.0, 2.8.3, 3.0.0
>
>         Attachments: HDFS-9914.001.patch, HDFS-9914.002.patch
>
>
> Webhdfs specific read/connect timeout as added HDFS-9887. This ticket is 
> opened to fix the following issues in current implementation:
> 1. The webhdfs read/connect timeout should not affect connection for other 
> callers of URLConnectionFactory.newSslConnConfigurator() such as 
> QuorumJournalManager#QuorumJournalManger(), DFSck#DFSck() and 
> TransferFsImage()
> 2. URLConnectionFactory#getSSLConnectionConfiguration() should honor webhdfs 
> connect/read timeout even if any exception is thrown during customized SSL 
> configuration. 
>  
> 3.  OAuth2 webhdfs connection should honor the webhdfs connect/read timeout.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to