Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-3007

DataNode pipelining : failure on mirror results in failure on upstream datanode

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

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.16.0
    • 0.16.2
    • None
    • None

    Description

      When datanode is transfering data to other datanodes (as opposed to a client write()), DN currently receiving the data is supposed to continued to receive even if the downstream (mirror) datanode fails.

      I think there are two minor bugs in receiveBlock() :

      1. mirrorSock masks this.mirrorSock, which could be set to null by other members like receiveChunk() to indicate failure.
      2. when this.mirrorSock is non null, failure to write to it at in receiveBlock() should be handled same way as in receiveChunk().

      I am not sure if this should block 0.16.1, but should surely block 0.16.2.

      Attachments

        1. HADOOP-3007.patch
          5 kB
          Raghu Angadi
        2. HADOOP-3007.patch
          5 kB
          Raghu Angadi

        Activity

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

          People

            rangadi Raghu Angadi
            rangadi Raghu Angadi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment