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] [Commented] (HDFS-10733) NameNode terminated after full GC thinking QJM is unresponsive.
Date Wed, 11 Jan 2017 21:35:16 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819253#comment-15819253

Konstantin Shvachko commented on HDFS-10733:

+1 on the latest patch.
Failed tests passed locally for me. Will commit in a bit.

> 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
>         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

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

View raw message