hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-10733) NameNode terminated after full GC thinking QJM is unresponsive.
Date Mon, 08 Aug 2016 23:35:20 GMT
Konstantin Shvachko created HDFS-10733:
------------------------------------------

             Summary: NameNode terminated after full GC thinking QJM is unresponsive.
                 Key: HDFS-10733
                 URL: https://issues.apache.org/jira/browse/HDFS-10733
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode, qjm
    Affects Versions: 2.6.4
            Reporter: Konstantin Shvachko


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message