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

Xiaoyu Yao commented on HDFS-9831:
----------------------------------

Thanks [~xiaobingo] for the update. One more issue found on the rendered 
webhdfs.html (changes in webhdfs.md)

I don't think we should put "The following properties control WebHDFS retry and 
failover policy." and the retry keys under the "Cross-Site Request Forgery 
Prevention" section. Can you add this as a separate section like below? 

{code}

WebHDFS Retry Policy
-------------------------------------

WebHDFS supports an optional, configurable retry policy for resilient copy of 
large files that could timeout, or copy file between HA clusters that could 
failover during the copy.

The following properties control WebHDFS retry and failover policy.
...

{code}

> Document webhdfs retry configuration keys introduced by HDFS-5219/HDFS-5122 
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-9831
>                 URL: https://issues.apache.org/jira/browse/HDFS-9831
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation, webhdfs
>    Affects Versions: 2.6.0
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaobing Zhou
>         Attachments: HDFS-9831.000.patch, HDFS-9831.001.patch
>
>
> This ticket is opened to document the configuration keys introduced by 
> HDFS-5219/HDFS-5122 for WebHdfs Retry.  Both hdfs-default.xml and webhdfs.md 
> should be updated with the usage of these keys.
> {code}
> / WebHDFS retry policy
>   public static final String  DFS_HTTP_CLIENT_RETRY_POLICY_ENABLED_KEY = 
> "dfs.http.client.retry.policy.enabled";
>   public static final boolean DFS_HTTP_CLIENT_RETRY_POLICY_ENABLED_DEFAULT = 
> false;
>   public static final String  DFS_HTTP_CLIENT_RETRY_POLICY_SPEC_KEY = 
> "dfs.http.client.retry.policy.spec";
>   public static final String  DFS_HTTP_CLIENT_RETRY_POLICY_SPEC_DEFAULT = 
> "10000,6,60000,10"; //t1,n1,t2,n2,...
>   public static final String  DFS_HTTP_CLIENT_FAILOVER_MAX_ATTEMPTS_KEY = 
> "dfs.http.client.failover.max.attempts";
>   public static final int    DFS_HTTP_CLIENT_FAILOVER_MAX_ATTEMPTS_DEFAULT = 
> 15;
>   public static final String  DFS_HTTP_CLIENT_RETRY_MAX_ATTEMPTS_KEY = 
> "dfs.http.client.retry.max.attempts";
>   public static final int    DFS_HTTP_CLIENT_RETRY_MAX_ATTEMPTS_DEFAULT = 10;
>   public static final String  DFS_HTTP_CLIENT_FAILOVER_SLEEPTIME_BASE_KEY = 
> "dfs.http.client.failover.sleep.base.millis";
>   public static final int    DFS_HTTP_CLIENT_FAILOVER_SLEEPTIME_BASE_DEFAULT 
> = 500;
>   public static final String  DFS_HTTP_CLIENT_FAILOVER_SLEEPTIME_MAX_KEY = 
> "dfs.http.client.failover.sleep.max.millis";
>   public static final int    DFS_HTTP_CLIENT_FAILOVER_SLEEPTIME_MAX_DEFAULT = 
> 15000;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to