You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (Jira)" <ji...@apache.org> on 2022/11/30 14:59:00 UTC

[jira] [Commented] (OOZIE-3678) Reduce the number of NameNode access when starting the Yarn job

    [ https://issues.apache.org/jira/browse/OOZIE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641372#comment-17641372 ] 

Hadoop QA commented on OOZIE-3678:
----------------------------------

PreCommit-OOZIE-Build started


> Reduce the number of NameNode access when starting the Yarn job
> ---------------------------------------------------------------
>
>                 Key: OOZIE-3678
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3678
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: 5.2.1
>            Reporter: Janos Makai
>            Assignee: Janos Makai
>            Priority: Major
>         Attachments: OOZIE-3678-001.patch
>
>
> Before Oozie starts the Yarn application it assembles the class path which's elements' paths are resolved with
> {code:java}
> remoteFS.resolvePath(p){code}
> which can cause slowness and high NameNode load.
> The intention is to make this path resolution configurable (ability to turn it on/off) via an Oozie configuration thus customers can turn it off when they experience job start slowness. Default value should result the new behaviour is active.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)