tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-490) Tajo can't use 'dfs.nameservices' based on namenode ha mode.
Date Fri, 10 Jan 2014 08:22:50 GMT

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

Hudson commented on TAJO-490:
-----------------------------

SUCCESS: Integrated in Tajo-master-build #4 (See [https://builds.apache.org/job/Tajo-master-build/4/])
TAJO-490: Tajo can't use 'dfs.nameservices' based on namenode ha mode. (jhjung: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=3937ca992c87b4e89a8056c2becef80066501698)
* tajo-dist/src/main/bin/tajo


> Tajo can't use 'dfs.nameservices' based on namenode ha mode.
> ------------------------------------------------------------
>
>                 Key: TAJO-490
>                 URL: https://issues.apache.org/jira/browse/TAJO-490
>             Project: Tajo
>          Issue Type: Bug
>          Components: conf and scripts
>    Affects Versions: 0.8-incubating
>            Reporter: Jaehwa Jung
>            Assignee: Jaehwa Jung
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-490.patch
>
>
> I tested tajo based on namenode ha mode. I set hdfs-site.xml as follows:
> {code:xml}
>   <property>
>     <name>dfs.nameservices</name>
>     <value>local-cluster</value>
>   </property>
>   <property>
>     <name>dfs.ha.namenodes.local-cluster</name>
>     <value>nn1,nn2</value>
>   </property>
>   <property>
>     <name>dfs.namenode.rpc-address.local-cluster.nn1</name>
>     <value>server01:9020</value>
>   </property>
>   <property>
>     <name>dfs.namenode.rpc-address.local-cluster.nn2</name>
>     <value>server02:9020</value>
>   </property>
>   <property>
>     <name>dfs.ha.automatic-failover.enabled</name>
>     <value>true</value>
>   </property>
>   ...... omit middle .....
> {code}
> But tajo deamons couldn't start up as follows:
> {code:xml}
> 2014-01-10 12:08:25,892 INFO  master.TajoMaster (TajoMaster.java:checkAndInitializeSystemDirectories(218))
- Tajo Root Directory: hdfs://local-cluster/tajo
> 2014-01-10 12:08:27,576 ERROR master.TajoMaster (TajoMaster.java:init(181)) - java.net.UnknownHostException:
local-cluster
> java.lang.IllegalArgumentException: java.net.UnknownHostException: local-cluster
>         at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:414)
>         at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:164)
>         at org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:129)
>         at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:448)
>         at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:410)
>         at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:128)
>         at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2308)
>         at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:87)
>         at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2342)
>         at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2324)
>         at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:351)
>         at org.apache.hadoop.fs.Path.getFileSystem(Path.java:194)
>         at org.apache.tajo.master.TajoMaster.checkAndInitializeSystemDirectories(TajoMaster.java:221)
>         at org.apache.tajo.master.TajoMaster.init(TajoMaster.java:161)
>         at org.apache.tajo.master.TajoMaster.main(TajoMaster.java:1060)
> Caused by: java.net.UnknownHostException: local-cluster
>         ... 15 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message