[
https://issues.apache.org/jira/browse/OOZIE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1027:
--------------------------------
Attachment: OOZIE-1027.patch
> Command line mr does not support NN/JT parameters properly
> ----------------------------------------------------------
>
> Key: OOZIE-1027
> URL: https://issues.apache.org/jira/browse/OOZIE-1027
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.0, trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: 3.3.0, trunk
>
> Attachments: OOZIE-1027.patch
>
>
> 1. command line mr requires deprecated properties: fs.default.name, and does
> not accept new property. when uses fs.defaultFS (or
> mapreduce.jobtracker.address) in job.properties file, oozie client returns
> error that namenode (or jobtracker) is not specified in conf.
> 2. After the cli mr job is submitted. it fails due to mapred.job.tracker
> property.
> ACTION[0000417-121012032305965-oozie-oozi-W@hadoop1] Error starting action
> [hadoop1]. ErrorType [FAILED], ErrorCode [JA010], Message [JA010: Property
> [mapred.job.tracker] not allowed in action [inline configuration]
> configuration]
> org.apache.oozie.action.ActionExecutorException: JA010: Property
> [mapred.job.tracker] not allowed in action [inline configuration]
> configuration
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.checkForDisallowedProps(JavaActionExecutor.java:191)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.parseJobXmlAndConfiguration(JavaActionExecutor.java:265)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.setupActionConf(JavaActionExecutor.java:279)
> at
> org.apache.oozie.action.hadoop.MapReduceActionExecutor.setupActionConf(MapReduceActionExecutor.java:119)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:649)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:881)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
