[
https://issues.apache.org/jira/browse/YARN-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324620#comment-16324620
]
Chris Douglas commented on YARN-7712:
-------------------------------------
Got it. The purpose of the timestamp is not security, but correctness. It does
not support applications that might specify a region of a dependency (e.g.,
download a segment of a log file being appended to) or on a dependency that
does not exist during submission. It is sufficient for static dependencies
(e.g., jars) that are uploaded prior to submission, and to avoid the NM linking
a stale version of a resource for a new container. The only security guarantees
come from the {{FileSystem}}.
You mentioned the REST APIs a couple times. Why are those problematic?
If this is purely for testing, one could use a {{FilterFileSystem}} that
returns a constant for the modification time, rather than modifying YARN...
> Add ability to ignore timestamps in localized files
> ---------------------------------------------------
>
> Key: YARN-7712
> URL: https://issues.apache.org/jira/browse/YARN-7712
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Reporter: Miklos Szegedi
> Assignee: Miklos Szegedi
>
> YARN currently requires and checks the timestamp of localized files and
> fails, if the file on HDFS does not match to the one requested. This jira
> adds the ability to ignore the timestamp based on the request of the client.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
