[
https://issues.apache.org/jira/browse/FALCON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307104#comment-14307104
]
Pallavi Rao commented on FALCON-1012:
-------------------------------------
Not exactly. From what I see from the logs and the definition, Oozie variables
are to be set slightly differently when using MapR. As [~rslysh] has pointed
out, nameNode=maprfs:/localhost:722 is wrong when using MapR and hence the
dryrun fails.
Oozie variables should be (as per
http://new.spryinc.com/blog/how-mapr-uses-its-own-storage-layer-and-what-means-oozie):
oozie.wf.application.path=maprfs:/<path>
jobTracker=maprfs:///
nameNode=maprfs:///
> Add support for MapR-FS
> -----------------------
>
> Key: FALCON-1012
> URL: https://issues.apache.org/jira/browse/FALCON-1012
> Project: Falcon
> Issue Type: New Feature
> Components: hadoop, oozie
> Affects Versions: 0.7
> Environment: single node mapr 4.0.1 cluster.
> mapr-oozie 4.0.1
> Reporter: Roman Slysh
> Attachments: falcon.application.log, standalone-cluster.xml
>
>
> Getting error when trying to submit and schedule the oozie process:
> $ bin/falcon entity -submitAndSchedule -type process -file
> examples/entity/filesystem/oozie-mr-process.xml
> Getting wrong conf parameter:
> nameNode=maprfs:/localhost:722
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
