[
https://issues.apache.org/jira/browse/FALCON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312323#comment-14312323
]
Roman Slysh commented on FALCON-1012:
-------------------------------------
The issue is that oozie getting nameNode property from falcon conf
file.(nameNode=maprfs:/localhost:7222, where 7222 is port of CLDB server)
That's not valid oozie nameNode property. Valid is nameNode=maprfs:///.
Also the question is why in logs we see that 'nameNode=maprfs:/localhost:722',
but not 'maprfs:/localhost:7222' like in configuration?
> 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)
