Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-4959

Decommission data nodes, There is no response

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.5-alpha
    • Fix Version/s: None
    • Component/s: ha, hdfs-client, namenode
    • Labels:
      None

      Description

      There is "dfs.hosts.exclude" configured before NN start. Active/Standby works well.

      1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN.
      2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log.

      There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI.

      But the decommission process is very very slow, it indicates it cannot finish forever.

      I do think this is a bug.

        Activity

        Fengdong Yu created issue -
        Fengdong Yu made changes -
        Field Original Value New Value
        Description There is dfs.hosts.exclude configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN.

        There is no
        Fengdong Yu made changes -
        Description There is dfs.hosts.exclude configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN.

        There is no
        There is dfs.hosts.exclude configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log.

        There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI.

        But the decommission process is very very slow, it indicates it cannot finish forever.
        Fengdong Yu made changes -
        Description There is dfs.hosts.exclude configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log.

        There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI.

        But the decommission process is very very slow, it indicates it cannot finish forever.
        There is "dfs.hosts.exclude" configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log.

        There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI.

        But the decommission process is very very slow, it indicates it cannot finish forever.


        Fengdong Yu made changes -
        Component/s ha [ 12316609 ]
        Fengdong Yu made changes -
        Description There is "dfs.hosts.exclude" configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log.

        There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI.

        But the decommission process is very very slow, it indicates it cannot finish forever.


        There is "dfs.hosts.exclude" configured before NN start. Active/Standby works well.

        1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN.
        2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log.

        There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI.

        But the decommission process is very very slow, it indicates it cannot finish forever.


        I do think this is a bug.

          People

          • Assignee:
            Unassigned
            Reporter:
            Fengdong Yu
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:

              Development