[
https://issues.apache.org/jira/browse/HDDS-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-5019:
-----------------------------
Summary: Inconsistent tmp bucket name on different nodes when Kerberos is
enabled (was: Fix Inconsistent BucketName problem when use tmp volume and
kerberos is enable!)
> Inconsistent tmp bucket name on different nodes when Kerberos is enabled
> ------------------------------------------------------------------------
>
> Key: HDDS-5019
> URL: https://issues.apache.org/jira/browse/HDDS-5019
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: zhengchenyu
> Assignee: zhengchenyu
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> I setup yarn cluster on ozone, and kerberos is enable. NodeManager can't
> download resource package in ContainerLocalizer stage, show error like this
> {code}
> 2021-03-22 19:56:42,004 WARN
> org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService:
> \{
> ofs://test1/tmp/hadoop-yarn/staging/$user/.staging/job_1616412423610_0008/job.splitmetainfo,
> 1616414199202, FILE, null } failed:
> hadoop-yarn/staging/$user/.staging/job_1616412423610_0008/job.splitmetainfo:
> No such file or directory!
> java.io.FileNotFoundException:
> hadoop-yarn/staging/$user/.staging/job_1616412423610_0008/job.splitmetainfo:
> No such file or directory!
> {code}
> The reason is that this wrong way to get user. For kerberos principal in
> different machine are not same, so
> UserGroupInformation.getCurrentUser().getUserName() are not same. Because
> kerberos principal's formate is "user/[email protected]"
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
