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

zhihai xu commented on YARN-1778:
---------------------------------

[~ozawa],
That is a good idea. Although we can increase 
"dfs.client.block.write.locateFollowingBlock.retries" in configuration file and 
the FileSystemRMStateStore will take the change in startInternal from the 
configuration file in the following code, it will affect all the other modules 
to take this change. That may not be feasible.
{code}
    Configuration conf = new Configuration(getConfig());
    fs = fsWorkingPath.getFileSystem(conf);
{code}
To increase the flexibility, we can create a new configuration to customize 
"dfs.client.block.write.locateFollowingBlock.retries" for 
FileSystemRMStateStore, which is similar as FS_RM_STATE_STORE_RETRY_POLICY_SPEC 
to customize "dfs.client.retry.policy.spec" for
FileSystemRMStateStore at the following code from startInternal:
{code}
String retryPolicy =
        conf.get(YarnConfiguration.FS_RM_STATE_STORE_RETRY_POLICY_SPEC,
          YarnConfiguration.DEFAULT_FS_RM_STATE_STORE_RETRY_POLICY_SPEC);
    conf.set("dfs.client.retry.policy.spec", retryPolicy);
{code}
I will implement a new patch based on this.
thanks for the suggestion.
zhihai

> TestFSRMStateStore fails on trunk
> ---------------------------------
>
>                 Key: YARN-1778
>                 URL: https://issues.apache.org/jira/browse/YARN-1778
>             Project: Hadoop YARN
>          Issue Type: Test
>            Reporter: Xuan Gong
>            Assignee: zhihai xu
>         Attachments: YARN-1778.000.patch
>
>




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

Reply via email to