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

DFSClient does not treat write timeout of 0 properly

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.17.0
    • 1.1.0, 0.21.0
    • None
    • None
    • Incompatible change, Reviewed
    • Zero values for dfs.socket.timeout and dfs.datanode.socket.write.timeout are now respected. Previously zero values for these parameters resulted in a 5 second timeout.

    Description

      dfs.datanode.socket.write.timeout is used for sockets to and from datanodes. It is 8 minutes by default. Some users set this to 0, effectively disabling the write timeout (for some specific reasons).

      When this is set to 0, DFSClient sets the timeout to 5 seconds by mistake while writing to DataNodes. This is exactly the opposite of real intention of setting it to 0 since 5 seconds is too short.

      Attachments

        1. HADOOP-5464.patch
          1 kB
          Raghu Angadi
        2. HADOOP-5464.branch1.patch
          1 kB
          Brandon Li

        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:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment