[
https://issues.apache.org/jira/browse/HDFS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019933#comment-13019933
]
Matt Foley commented on HDFS-1829:
----------------------------------
In test build 366, we see TestNodeCount fail with NullPointerException in
BlockManager. (ref
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/366//testReport/org.apache.hadoop.hdfs.server.namenode/TestNodeCount/testNodeCount/
)
Such an error certainly can be caused by lack of synchronization. This patch [
12476098 ] should address it.
> TestNodeCount waits forever, errs without giving information
> ------------------------------------------------------------
>
> Key: HDFS-1829
> URL: https://issues.apache.org/jira/browse/HDFS-1829
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Matt Foley
> Assignee: Matt Foley
> Fix For: 0.23.0
>
> Attachments: TestNodeCount.java.patch
>
>
> In three locations in the code, TestNodeCount waits forever on a condition.
> Failures result in Hudson/Jenkins "Timeout occurred" error message with no
> information about where or why. Need to replace with TimeoutExceptions that
> throw a stack trace and useful info about the failure mode.
> Also investigate possible cause of failure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
