Hey, If you use the oozie.launcher prefix on a property, that property will be applied to the Launcher MR job, that launches the action. In your example if you set mapreduce.job.complete.cancel.delegation.tokens to false in the action's configuration then Sqoop will get this property, but the Launcher Mapper job isn't. If you set oozie.launcher. mapreduce.job.complete.cancel.delegation.tokens to false there, then the launcher job gets it.
I hope this helps, gp On Mon, Nov 7, 2016 at 11:38 AM, Андрей Ривкин <[email protected]> wrote: > Maybe u could tell me some books or where in documentation I can read about > it? > > Regards, > Andrey > > 2016-11-02 10:02 GMT+03:00 Андрей Ривкин <[email protected]>: > > > Hello everyone, > > > > Could somebody explain me how properties in oozie work? > > > > I've got java action on CDH 5.3 which generates a lot Sqoop actions and > we > > have problem with delegation tokens (https://issues.apache.org/jir > > a/browse/YARN-2964). This job works for 20 mins and always fails with > > delegation token not found in cache when tring to agregate logs. So we > even > > can't see logs. > > > > I've tried to set "mapreduce.job.complete.cancel.delegation.tokens" to > > false in java action and in whole workflow, but it didn't set. > > Then I've tried to set some custom propertie, for examle > > "some.custom.property=true", but it also didn't set. > > Then I've tried to change some oozie property, for example > > "oozie.launcher.mapreduce.map.memory.mb" and it worked. > > > > So I'm confused how oozie is working with job properties. > > > > I'm checking all properties in JobHistory -> configuration. > > > > > > > > Regards, > > Andrey > > > -- Peter Cseh Software Engineer <http://www.cloudera.com>
