Hello,

Running on oozie 4.1.0 with Hadoop 2.6.0.

When running the simple oozie hive example on a "VM Ware" Centos I see that the 
job transitions to RUNNING never ends and the state goes to UNASSIGNED.

It never exits that state.

On research it looks like I have to configure my yarn-site.xml to increase 
memory.  Not sure about how to tune this to run on VMWare.

 <property>
    <name> yarn.nodemanager.aux-services</name>
   <value>mapreduce_shuffle</value>
</property>
<property>
    <name>yarn.nodemanager.aux-services.mapreduce_shuffle.class</name>
    <value>org.apache.hadoop.mapred.ShuffleHandler</value>
 </property>
 <property>
    <name>yarn.nodemanager.resource.memory-mb</name>
   <value>2200</value>
  </property>
<property>
   <name>yarn.scheduler.minimum-allocation-mb</name>
   <value>500</values>
</property>

Could do with a little guidance on this.

Thanks,
Gazza


Reply via email to