hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9145) Tracking methods that hold FSNamesytemLock for too long
Date Thu, 25 Aug 2016 21:44:21 GMT

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

Kihwal Lee commented on HDFS-9145:

There is a test failure in branch-2.7 after this.
 T E S T S
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in
Running org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem
Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.741 sec <<< FAILURE!
- in org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem
testFSLockGetWaiterCount(org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem)  Time elapsed:
0.004 sec  <<< FAILURE!
java.lang.AssertionError: Expected number of blocked thread not found expected:<3> but
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:743)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:555)
	at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.testFSLockGetWaiterCount(TestFSNamesystem.java:244)

It seems to pass when this test case is run separately. It might be due to interactions with
other tests in the suite.

> Tracking methods that hold FSNamesytemLock for too long
> -------------------------------------------------------
>                 Key: HDFS-9145
>                 URL: https://issues.apache.org/jira/browse/HDFS-9145
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Jing Zhao
>            Assignee: Mingliang Liu
>             Fix For: 2.8.0, 2.7.4
>         Attachments: HDFS-9145.000.patch, HDFS-9145.001.patch, HDFS-9145.002.patch, HDFS-9145.003.patch
> It will be helpful that if we can have a way to track (or at least log a msg) if some
operation is holding the FSNamesystem lock for a long time.

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