This is not cause of Oozie, but cause of the way MR runs. Unless you turn on the LinuxTaskController (MR1) or the LinuxContainerExecutor (YARN+MR2) all task JVMs are spawned as the user that runs the TaskTracker (mapred)/NodeManager (yarn), and thereby any non-HDFS work done in these tasks (such as local FS writes/etc.) will be done only as that user.
You should be able to configure LTC/LCE without turning on full security to have MR run task JVMs as the actual submitting user (this needs unix lookup-able accounts of the user on all processing hosts though, either manually or via ldap/etc.). You can email the Hadoop user group ([email protected]) for further questions on this. On Wed, Mar 25, 2015 at 5:46 PM, Bhagaban Khatai <[email protected]> wrote: > Hello, > > Can someone update how I cna change the user (who submit the oozie job) > from mapred user. > > I want to write some logs in a directory but bydefault it's taking mapred > user but the requirement is whoever submit the oozie job that user should > reflect in the log files. > > Please help me! > -- Harsh J
