[
https://issues.apache.org/jira/browse/YARN-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389613#comment-15389613
]
Jason Lowe commented on YARN-5423:
----------------------------------
This sounds like a bug in the user re-creation procedure rather than YARN. If a
user with user ID = 1234 creates some files then we delete and re-create the
user with user ID = 5678 then not just YARN is going to have issues. Any local
files in the OS that were created with the old user ID will not be accessible
via the new user ID if they are private (e.g.: mode 0700 or something like
that). That's not just a YARN thing.
The user ID needs to be preserved when it is re-created or all paths belonging
to the old user need to be chowned when the new user ID is created.
> Yarn applications are failing when job submitter use is re-created in OS.
> -------------------------------------------------------------------------
>
> Key: YARN-5423
> URL: https://issues.apache.org/jira/browse/YARN-5423
> Project: Hadoop YARN
> Issue Type: Bug
> Components: applications
> Affects Versions: 2.7.1
> Reporter: Surendra Singh Lilhore
>
> When we re-create user in OS, user ID may change. If we run application from
> the same user again, application will not able to write data in user NM local
> directory
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
