You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/04/15 02:30:59 UTC

[jira] [Commented] (KNOX-530) Running Oozie jobs through Knox on a cluster with HDFS HA does not rewrite proper namenode host name.

    [ https://issues.apache.org/jira/browse/KNOX-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495237#comment-14495237 ] 

ASF subversion and git services commented on KNOX-530:
------------------------------------------------------

Commit cc27d465e116ff7445b562dcb421ad96f717f8e0 in knox's branch refs/heads/master from [~sumit.gupta]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=cc27d46 ]

KNOX-530 fixed oozie rewrite rules to handle missing port information


> Running Oozie jobs through Knox on a cluster with HDFS HA does not rewrite proper namenode host name.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: KNOX-530
>                 URL: https://issues.apache.org/jira/browse/KNOX-530
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Sumit Gupta
>            Assignee: Sumit Gupta
>             Fix For: 0.6.0, 0.7.0
>
>
> When running Oozie jobs through Knox on a cluster with HDFS HA, one can use the logical HA service name for namenode. The workflow configuration file does not get rewritten properly if the logical name is used as it does not have a port in it.
> For example in the following workflow configuration file:
> {code:xml}
> <configuration>
>     <property>
>         <name>jobTracker</name>
>         <value>JOBTRACKER</value>
>         <!-- Example: <value>localhost:50300</value> -->
>     </property>
>     <property>
>         <name>nameNode</name>
>         <value>NAMENODE</value>
>         <!-- Example: <value>hdfs://localhost:8020</value> -->
>     </property>
>     <property>
>         <name>oozie.wf.application.path</name>
>         <value>/user/guest/example</value>
>         <!-- Example: <value>hdfs://localhost:8020/tmp/test</value> -->
>     </property>
>     <property>
>         <name>user.name</name>
>         <value>mapred</value>
>     </property>
>     <property>
>         <name>inputDir</name>
>         <value>/user/guest/example/input</value>
>     </property>
>     <property>
>         <name>outputDir</name>
>         <value>/user/guest/example/output</value>
>     </property>
> </configuration>
> {code}
> and topology file containing the following namenode service :
> {code:xml}
>  <service>
>                 <role>NAMENODE</role>
>                 <url>hdfs://ha-service</url>
>             </service>
> {code}
> and the command :
> curl -i -k -u guest:guest-password -H Content-Type:application/xml -T workflow-configuration.xml     -X POST 'https://localhost:8443/gateway/sandbox/oozie/v1/jobs?action=start'
> results in the following oozie error
> E0902: Exception occured: [Incomplete HDFS URI, no host: hdfs://ha-service:NAMENODE/user/guest/example]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)