You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2016/08/08 23:35:20 UTC
[jira] [Created] (HDFS-10733) NameNode terminated after full GC
thinking QJM is unresponsive.
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org