[jira] [Commented] (HDFS-4633) TestDFSClientExcludedNodes fails sporadically if excluded nodes cache expires too quickly

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on HDFS-4633:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #4679 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4679/])
HDFS-4633. Change attribution in CHANGES.txt to version 2.2.1. (cnauroth: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1537345)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> TestDFSClientExcludedNodes fails sporadically if excluded nodes cache expires too quickly
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-4633
>                 URL: https://issues.apache.org/jira/browse/HDFS-4633
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client, test
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 3.0.0, 2.2.1
>
>         Attachments: HDFS-4633.1.patch, HDFS-4633.2.patch, HDFS-4633.3.patch
>
>
> {{TestDFSClientExcludedNodes}} simulates failures of individual data nodes in the client's write pipeline and checks the client's ability to recover.  HDFS-4246 added support for periodic "forgiveness" by caching the list of known bad data nodes with a periodic eviction.  The test uses a 1 second cache expiration.  This sometimes causes failed nodes to be forgiven too fast and violate the assumptions of the test.



--
This message was sent by Atlassian JIRA
(v6.1#6144)