Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-3091

Update the usage limitations of ReplaceDatanodeOnFailure policy in the config description for the smaller clusters.

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.23.0, 2.0.0-alpha
    • 2.0.0-alpha
    • datanode, hdfs-client, namenode
    • None
    • Reviewed

    Description

      When verifying the HDFS-1606 feature, Observed couple of issues.

      Presently the ReplaceDatanodeOnFailure policy satisfies even though we dont have enough DN to replcae in cluster and will be resulted into write failure.

      12/03/13 14:27:12 WARN hdfs.DFSClient: DataStreamer Exception
      java.io.IOException: Failed to add a datanode: nodes.length != original.length + 1, nodes=[xx.xx.xx.xx:50010], original=[xx.xx.xx.xx1:50010]
      at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.findNewDatanode(DFSOutputStream.java:778)
      at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.addDatanode2ExistingPipeline(DFSOutputStream.java:834)
      at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.setupPipelineForAppendOrRecovery(DFSOutputStream.java:930)
      at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(DFSOutputStream.java:741)
      at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:416)

      Lets take some cases:
      1) Replication factor 3 and cluster size also 3 and unportunately pipeline drops to 1.

      ReplaceDatanodeOnFailure will be satisfied because existings(1)<= replication/2 (3/2==1).

      But when it finding the new node to replace obiously it can not find the new node and the sanity check will fail.

      This will be resulted to Wite failure.

      2) Replication factor 10 (accidentally user sets the replication factor to higher value than cluster size),
      Cluser has only 5 datanodes.

      Here even if one node fails also write will fail with same reason.
      Because pipeline max will be 5 and killed one datanode, then existings will be 4

      existings(4)<= replication/2(10/2==5) will be satisfied and obiously it can not replace with the new node as there is no extra nodes exist in the cluster. This will be resulted to write failure.

      3) sync realted opreations also fails in this situations ( will post the clear scenarios)

      Attachments

        1. h3091_20120319.patch
          0.8 kB
          Tsz-wo Sze

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            szetszwo Tsz-wo Sze
            umamaheswararao Uma Maheswara Rao G
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment