[
https://issues.apache.org/jira/browse/HDFS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277825#comment-13277825
]
Hudson commented on HDFS-3422:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1082 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1082/])
HDFS-3422. TestStandbyIsHot timeouts too aggressive. Contributed by Todd
Lipcon. (Revision 1339452)
Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1339452
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestStandbyIsHot.java
> TestStandbyIsHot timeouts too aggressive
> ----------------------------------------
>
> Key: HDFS-3422
> URL: https://issues.apache.org/jira/browse/HDFS-3422
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 2.0.1
>
> Attachments: hdfs-3422.txt
>
>
> I've seen TestStandbyIsHot timeout a few times waiting for replication to
> change, but when I look at the logs, it appears everything is fine. The block
> deletions are just a bit slow in being processed.
> To improve the test we should either increase the timeouts, or explicitly
> trigger heartbeats and replication work after changing the desired
> replication levels.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
