See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk/562/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 573269 lines...]
[junit] 2011-01-25 12:15:42,80
Move secondary namenode checkpoint configs from core-default.xml to
hdfs-default.xml
Key: HDFS-1596
URL: https://issues.apache.org/jira/browse/HDFS-1596
Project: Had
Misplaced assertion in FSEditLog.logSync
Key: HDFS-1597
URL: https://issues.apache.org/jira/browse/HDFS-1597
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.22.0
Reporter: Tod
Hi, guys,
Do we have any plan to enable VIP between NameNode and DataNodes, I mean
multiple NameNodes and we use a VIP stands before the NNs. Then DNs only
need to connect to the VIP. I don't know if it is valuable we have this impl
in our hdsf and if there has any issues?
Any hints are valuable
This is a good approach, is used by many to mask the NameNode address
for the DataNodes; and is also good to use while using BackupNode
(Even Facebook does this).
On Wed, Jan 26, 2011 at 7:38 AM, mac fang wrote:
> Hi, guys,
>
> Do we have any plan to enable VIP between NameNode and DataNodes, I m
Thanks, Harsh.
Any issues you see if we use this? I've already done some researches of this
approach. However i am NOT sure if there has some potential risks if we use
VIP (i am NOT a seasoned hadooper :) )
regards
macf
On Wed, Jan 26, 2011 at 10:12 AM, Harsh J wrote:
> This is a good approach
Fb does not use the VIP approach, we tried that but quickly found out some
limitations, one main problem being that the failover server pair has to be
in the same subnet (for VIP to work). Instead we now use the AvatarNode
integrated with Zookeeper.
-dhruba
On Tue, Jan 25, 2011 at 6:12 PM, Harsh
