Configuring correct port for Oozie (invoking PIG script) in Cloudera Hue
        Posted  
        
            by 
                user2985324
            
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by user2985324
        
        
        
        Published on 2013-11-12T22:48:17Z
        Indexed on 
            2013/11/13
            15:54 UTC
        
        
        Read the original article
        Hit count: 1661
        
I am new to CDH4 Oozie workflow editor. While trying to invoke a pig script from Oozie workflow editor, i am getting the following error.
HadoopAccessorException: E0900: Jobtracker [mymachine:8032] not allowed, not in Oozies whitelist
It looks like Oozie is submitting the job to Yarn port (8032). I want it to submit to 8021 (MR jobtracker) port. Can someone help me in identify where to set the job tracker URL or port so that oozie picks up the correct one (using Hue or Cloudera manager).
Previously I tried the following but none of them helped
Modfied workflow.xml file /user/hue/oozie/workspaces/../workflow.xml file. However it gets overwritten when I submit the job from workflow editor.
In cloudera Manager --> oozie --> configuration -->Oozie Server (advanced) --> Oozie Server Configuration Safety Valve for oozie-site.xml property I set the following-
<property> <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name> <value>mymachine:8020</value>oozie.service.HadoopAccessorService.jobTracker.whitelist mymachine:8021
and restarted the oozie service. 3. Tried to override 'jobTracker' property while configuring the pig task. This appears as follows in the workflow file however it doesn't take effect (or doesn't override) and still uses 8032 port.
<global>
            <configuration>
                <property>
                    <name>jobTracker</name>
                    <value>mymachine:8021</value>
                </property>
            </configuration>
 </global>
I am using CDH4 version.
Thanks for looking into my question.
© Stack Overflow or respective owner