hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1129) Allow HDFS DataNodes and NameNode to have different build versions
Date Wed, 05 May 2010 05:20:05 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864159#action_12864159

dhruba borthakur commented on HDFS-1129:

The NameNode checks whether the build version of a datanode matches the build version of the
namenode. I propose that we do the following:

1. The namenode should ensure that datanodes match the namenode's build version if the value
of a configuration parameter is set to true. Otherwise, it avoids doing this check. 

2. The default value of this config parameter would be set to true.

3. The webUi and "dfsadmin -report" should display the build versions reported by the datanodes.

The above functionality is also useful to support hot-standby namenode, via HDFS-976

> Allow HDFS DataNodes and NameNode to have different build versions
> ------------------------------------------------------------------
>                 Key: HDFS-1129
>                 URL: https://issues.apache.org/jira/browse/HDFS-1129
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: dhruba borthakur
> There are times when we want to deploy fixes to the NameNode without restarting the DataNodes.
This reduces the restart time of the entire cluster.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message