FAQ
Remove a datanode from cluster if include list is not empty and this datanode is removed from both include and exclude lists
----------------------------------------------------------------------------------------------------------------------------

Key: HDFS-1773
URL: https://issues.apache.org/jira/browse/HDFS-1773
Project: Hadoop HDFS
Issue Type: Improvement
Affects Versions: 0.20.203.1
Environment: branch-20-security

Reporter: Tanping Wang
Assignee: Tanping Wang
Fix For: 0.20.4


Our service engineering team who operates the clusters on a daily basis founds it is confusing that after a data node is decommissioned, there is no way to make the cluster forget about this data node and it always remains in the dead node list.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Search Discussions

  • Tsz Wo (Nicholas), SZE (JIRA) at Mar 24, 2011 at 8:29 pm
    [ https://issues.apache.org/jira/browse/HDFS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Tsz Wo (Nicholas), SZE resolved HDFS-1773.
    ------------------------------------------

    Resolution: Fixed
    Fix Version/s: (was: 0.20.4)
    0.20.204
    Hadoop Flags: [Reviewed]

    I have committed this to 0.20-security. Thanks, Tanping!
    Remove a datanode from cluster if include list is not empty and this datanode is removed from both include and exclude lists
    ----------------------------------------------------------------------------------------------------------------------------

    Key: HDFS-1773
    URL: https://issues.apache.org/jira/browse/HDFS-1773
    Project: Hadoop HDFS
    Issue Type: Improvement
    Affects Versions: 0.20.203.1
    Environment: branch-20-security
    Reporter: Tanping Wang
    Assignee: Tanping Wang
    Priority: Minor
    Fix For: 0.20.204

    Attachments: HDFS-1773-2.patch, HDFS-1773-3.patch, HDFS-1773.patch


    Our service engineering team who operates the clusters on a daily basis founds it is confusing that after a data node is decommissioned, there is no way to make the cluster forget about this data node and it always remains in the dead node list.
    --
    This message is automatically generated by JIRA.
    For more information on JIRA, see: http://www.atlassian.com/software/jira
  • Tanping Wang (JIRA) at May 2, 2011 at 9:19 pm
    [ https://issues.apache.org/jira/browse/HDFS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Tanping Wang reopened HDFS-1773:
    --------------------------------


    Port this jira to trunk. Mark HDFS-1867 as a duplication of this jira.
    Remove a datanode from cluster if include list is not empty and this datanode is removed from both include and exclude lists
    ----------------------------------------------------------------------------------------------------------------------------

    Key: HDFS-1773
    URL: https://issues.apache.org/jira/browse/HDFS-1773
    Project: Hadoop HDFS
    Issue Type: Improvement
    Affects Versions: 0.20.203.1
    Environment: branch-20-security
    Reporter: Tanping Wang
    Assignee: Tanping Wang
    Priority: Minor
    Fix For: 0.20.204.0

    Attachments: HDFS-1773-2.patch, HDFS-1773-3.patch, HDFS-1773.patch


    Our service engineering team who operates the clusters on a daily basis founds it is confusing that after a data node is decommissioned, there is no way to make the cluster forget about this data node and it always remains in the dead node list.
    --
    This message is automatically generated by JIRA.
    For more information on JIRA, see: http://www.atlassian.com/software/jira

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouphdfs-dev @
categorieshadoop
postedMar 21, '11 at 10:25p
activeMay 2, '11 at 9:19p
posts3
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Tanping Wang (JIRA): 3 posts

People

Translate

site design / logo © 2022 Grokbase