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

FSCK fails if one namenode is not available

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.3.0, 3.2.2
    • None
    • None
    • Reviewed

    Description

      If one namenode is not available FSCK should try on other namenode, ignoring the namenode not available

      Attachments

        1. HDFS-15223-01.patch
          2 kB
          Ayush Saxena
        2. HDFS-15223-02.patch
          3 kB
          Ayush Saxena

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

          People

            ayushtkn Ayush Saxena
            ayushtkn Ayush Saxena
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment