[jira] [Created] (HDDS-5019) BucketName are not same for different host's ozone client, when use tmp volume and kerberos is enable!

["zhengchenyu (Jira)" <ji...@apache.org>]

zhengchenyu created HDDS-5019:
---------------------------------

             Summary: BucketName are not same for different host's ozone client,  when use tmp volume and kerberos is enable!
                 Key: HDDS-5019
                 URL: https://issues.apache.org/jira/browse/HDDS-5019
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: zhengchenyu


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.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org