[
https://issues.apache.org/jira/browse/HDFS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018715#comment-13018715
]
Matt Foley commented on HDFS-1829:
----------------------------------
Converted the infinite waits to 20 second timeouts with informative
TimeoutException message info.
I did not find an obvious explanation for the failure, but did find that only
one of three calls to namesystem.blockManager.countNodes(block) was correctly
synchronized on namesystem. Fixed the other two, following the same pattern.
Although, in retrospect, all three really should be replaced by readLock()
calls. I'll fix that in the next version.
> 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
