Hadoop Common
  1. Hadoop Common
  2. HADOOP-4862

A spurious IOException log on DataNode is not completely removed

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.18.2
    • Fix Version/s: 0.19.1
    • Component/s: None
    • Labels:
      None
    • Environment:
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions logged by DataNode.
      Show
      Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions logged by DataNode.

      Description

      HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still possible in some cases.

      For e.g. The exception is still logged if the client closes the connection after DataNode writes all the block data but before it writes final 4 bytes to indicate end of data.

      1. HADOOP-4862.patch
        3 kB
        Raghu Angadi
      2. HADOOP-4862.patch
        3 kB
        Raghu Angadi
      3. HADOOP-4862-branch-18.patch
        3 kB
        Raghu Angadi

        Issue Links

          Activity

          Raghu Angadi created issue -
          Raghu Angadi made changes -
          Field Original Value New Value
          Link This issue relates to HADOOP-3678 [ HADOOP-3678 ]
          Raghu Angadi made changes -
          Attachment HADOOP-4862-branch-18.patch [ 12395977 ]
          Raghu Angadi made changes -
          Attachment HADOOP-4862.patch [ 12396138 ]
          Raghu Angadi made changes -
          Description
          HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still possible in some cases.

          For e.g. The exception is still logged if the client closes the connection after DataNode writes all the block data but before it writes final 4 bytes to indicate end of data.
          HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still possible in some cases.

          For e.g. The exception is still logged if the client closes the connection after DataNode writes all the block data but before it writes final 4 bytes to indicate end of data.
          Priority Major [ 3 ] Blocker [ 1 ]
          Raghu Angadi made changes -
          Attachment HADOOP-4862.patch [ 12398438 ]
          Raghu Angadi made changes -
          Summary A spuriou IOException log on DataNode is not completely removed A spurious IOException log on DataNode is not completely removed
          Environment Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions logged by DataNode.
          Raghu Angadi made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Raghu Angadi made changes -
          Hadoop Flags [Reviewed]
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Release Note Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions logged by DataNode.
          Resolution Fixed [ 1 ]
          Nigel Daley made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Owen O'Malley made changes -
          Component/s dfs [ 12310710 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development