Hadoop Common
  1. Hadoop Common
  2. HADOOP-3339

DFS Write pipeline does not detect defective datanode correctly if it times out.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.16.0
    • Fix Version/s: 0.18.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      Improved failure handling of last Data Node in write pipeline.
      Show
      Improved failure handling of last Data Node in write pipeline.

      Description

      When DFSClient is writing to DFS, it does not correctly detect the culprit datanode (rather datanodes do not inform) properly if the bad node times out. Say, the last datanode in in 3 node pipeline is is too slow or defective. In this case, pipeline removes the first two datanodes in first two attempts. The third attempt has only the 3rd datanode in the pipeline and it will fail too. If the pipeline detects the bad 3rd node when the first failure occurs, the write will succeed in the second attempt.

      I will attach example logs of such cases. I think this should be fixed in 0.17.x.

      1. HADOOP-3339.patch
        3 kB
        Raghu Angadi
      2. tmp-3339-dn.patch
        1 kB
        Raghu Angadi

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Raghu Angadi
              Reporter:
              Raghu Angadi
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development