[
https://issues.apache.org/jira/browse/HDFS-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091150#comment-16091150
]
Jiandan Yang commented on HDFS-10733:
--------------------------------------
[~redvine] I would like to ask you a question for the following code. When the
fullgc time has far exceeded the value of 'millis', (et + millis) will be
negative and then a TimeoutException will be thrown. How about et=now+millis?
{code:java}
if (shouldIncreaseQuorumTimeout(-rem, millis)) {
et = et + millis;
}
{code}
> 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
> Assignee: Vinitha Reddy Gankidi
> Fix For: 2.8.0, 2.9.0, 2.7.4, 3.0.0-alpha2
>
> Attachments: HDFS-10733.001.patch, HDFS-10733.002.patch
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
