Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      DFSOutputStream.handleSocketException() does not handle exceptions thrown inside it
      by abandonBlock(). I'd propose to retry abandonBlock() in case of timeout.
      In case of DFSOutputStream.close() the exception in handleSocketException() will result in
      calling abandonFileInProgress().
      In a similar case of DFSOutputStream.flush() the file will not be abandoned.
      Exceptions thrown by abandonFileInProgress() are not handled either.

      Feels like we need a general mechanism for handling all these things.

        Activity

        Hide
        Harsh J added a comment -

        This has gone stale. I do not find these methods in the current DFSOutputStream. Do open a new one if there is still trouble with the newer impl.

        Show
        Harsh J added a comment - This has gone stale. I do not find these methods in the current DFSOutputStream. Do open a new one if there is still trouble with the newer impl.

          People

          • Assignee:
            Unassigned
            Reporter:
            Konstantin Shvachko
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development