hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4633) TestDFSClientExcludedNodes fails sporadically if excluded nodes cache expires too quickly
Date Mon, 25 Mar 2013 20:11:17 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HDFS-4633:
--------------------------------

    Attachment: HDFS-4633.1.patch

With this patch, the test passes consistently on every machine I've tried.  The changes are:

# Guarantee that each test properly shuts down its {{MiniDFSCluster}}.
# Increase timeouts in test annotations from 10s to 60s.  These timeouts were too tight and
even caused sporadic failures on my fastest machine.
# Increase excluded nodes cache expiry from 1s to 10s.  I expect this is plenty of time for
any machine to make it through the loop in {{DFSOutputStream#DataStreamer#nextBlockOutputStream}}.

                
> 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
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-4633.1.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message