[
https://issues.apache.org/jira/browse/HDFS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021687#comment-13021687
]
Eli Collins commented on HDFS-1829:
-----------------------------------
How about handling these as is done for HDFS-1562? You could augment
NameNodeAdapter#getReplicaInfo to return excess and live replica counts as well
and then just add waitFor[Live|Excess]Replicas methods to DFSTestUtil and have
TestNodeCount call them. This way we could re-use them in the other replication
tests.
> 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: 1829_TestNodeCount_v4.patch, TestNodeCount.java.patch,
> TestNodeCount_v2.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
