Hi Alexy, That is correct, putting the RM address instead of the JobTracker will work. By "Oozie is configured for MRv2", they mean that Oozie has to have the Hadoop 2/YARN jars instead of the Hadoop 1 jars. If you build Oozie with the "hadoop-2" profile, it will use the jars from hadoop 2.2.0-SNAPSHOT.
OOZIE-1551 <https://issues.apache.org/jira/browse/OOZIE-1551> will make the "hadoop-2" profile in Oozie 4.0.1 (when its released) use Hadoop 2.1.1-beta, which is probably more similar to what you're using. In any case, you can also manually replace the Hadoop jars with the corresponding Hadoop 2.x jars from your Hadoop installation and that should work. thanks - Robert On Wed, Sep 25, 2013 at 4:00 PM, Alexey Yakubovich <[email protected]>wrote: > Hi, > > It is well known that Yarn/MRv2 does not have job tracker. I found on the > grokbase posting "Migration of Oozoe jos to Yarn - > > http://grokbase.com/t/cloudera/cdh-user/12can8y32b/migration-of-oozie-jobs-to-yarn-mr2 > " > that e.g. job.properties file still suppose to specify the jobTracker > property, but actual port/host should point to the RM, and port (usually) > is 8032. But it still does not work for me. > Also that posting said "things should still work if your Oozie is > configured for MRv2". > > Now, what that means: Oozie is configured for MRv2? And are there any other > (configuration) changes you would need to make moving to Oozie 4.0? And can > anybody share the valid Oozie 4.0 job.properties file, please? > > Thank you > Alexey >
