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

NameNode terminated after full GC thinking QJM is unresponsive.

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

Details

    • Reviewed

    Description

      NameNode went into full GC while in AsyncLoggerSet.waitForWriteQuorum(). After completing GC it checks if the timeout for quorum is reached. If the GC was long enough the timeout can expire, and QuorumCall.waitFor() will throw TimeoutExcpetion. Finally FSEditLog.logSync() catches the exception and terminates NameNode.

      Attachments

        1. HDFS-10733.001.patch
          4 kB
          Vinitha Reddy Gankidi
        2. HDFS-10733.002.patch
          4 kB
          Vinitha Reddy Gankidi

        Issue Links

        Activity

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

          People

            redvine Vinitha Reddy Gankidi
            shv Konstantin Shvachko
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment