[
https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148255#comment-14148255
]
Zhijie Shen commented on YARN-2606:
-----------------------------------
The right fix may be moving the FS operations to serviceStart(). See the
similar code in FileSystemRMStateStore:
{code}
@Override
protected synchronized void startInternal() throws Exception {
// create filesystem only now, as part of service-start. By this time, RM is
// authenticated with kerberos so we are good to create a file-system
// handle.
Configuration conf = new Configuration(getConfig());
conf.setBoolean("dfs.client.retry.policy.enabled", true);
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);
fs = fsWorkingPath.getFileSystem(conf);
fs.mkdirs(rmDTSecretManagerRoot);
fs.mkdirs(rmAppRoot);
fs.mkdirs(amrmTokenSecretManagerRoot);
}
{code}
BTW, we're thinking about removing the old application history store stack
(YARN-2320).
> Application History Server tries to access hdfs before doing secure login
> -------------------------------------------------------------------------
>
> Key: YARN-2606
> URL: https://issues.apache.org/jira/browse/YARN-2606
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Affects Versions: 2.6.0
> Reporter: Mit Desai
> Assignee: Mit Desai
> Attachments: YARN-2606.patch
>
>
> While testing the Application Timeline Server, the server would not come up
> in a secure cluster, as it would keep trying to access hdfs without having
> done the secure login. It would repeatedly try authenticating and finally hit
> stack overflow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
