Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-11087

NamenodeFsck should check if the output writer is still writable.

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.6.5
    • 2.8.0, 2.7.4
    • namenode
    • None
    • Reviewed

    Description

      NamenodeFsck keeps running even after the client was interrupted. So if you start fsck / on a large namespace and kill the client, the NameNode will keep traversing the tree for hours although there is nobody to receive the result.

      Attachments

        1. HDFS-11087.branch-2.000.patch
          0.9 kB
          Erik Krogen
        2. HDFS-11087-branch-2.000.patch
          0.9 kB
          Erik Krogen
        3. HDFS-11087-branch-2.001.patch
          1 kB
          Erik Krogen

        Activity

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

          People

            xkrogen Erik Krogen
            shv Konstantin Shvachko
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment