hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira Ajisaka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11352) Potential deadlock in NN when failing over
Date Thu, 16 Feb 2017 02:32:41 GMT

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

Akira Ajisaka commented on HDFS-11352:

Hi [~yzhangal], yes, it's correct.

> Potential deadlock in NN when failing over
> ------------------------------------------
>                 Key: HDFS-11352
>                 URL: https://issues.apache.org/jira/browse/HDFS-11352
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.7.4, 2.6.6
>            Reporter: Erik Krogen
>            Assignee: Erik Krogen
>            Priority: Critical
>              Labels: high-availability
>             Fix For: 2.7.4, 2.6.6
>         Attachments: HDFS-11352-branch-2.7.000.patch
> HDFS-11180 fixed a general class of deadlock that can occur when failing over  between
the MetricsSystemImpl and FSEditLog (see comments on that JIRA for more details). In trunk
and branch-2/branch-2.8 this fix was successful by making the metrics calls not synchronize
on FSEditLog.
> In branch-2.6 and branch-2.7 there is one more method, {{FSNamesystem#getTransactionsSinceLastCheckpoint}},
which still requires the lock on FSEditLog and thus can result in the same deadlock scenario.
This can be seen by running {{TestFSNamesystemMBean#testWithFSEditLogLock}} _with the patch
in HDFS-11290_ on either of these branches (it fails currently).

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