hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Clampffer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9890) libhdfs++: Add test suite to simulate network issues
Date Wed, 30 Mar 2016 18:31:25 GMT

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

James Clampffer updated HDFS-9890:
----------------------------------
    Attachment: HDFS-9890.HDFS-8707.000.patch

Initial patch, right now error injection is turned on and off with "#ifdef ENABLE_RPC_ERROR_SIMULATION".

I think the hooks added in HDFS-9616 are the best way to trigger these conditions and give
better control in more complicated tests.

> libhdfs++: Add test suite to simulate network issues
> ----------------------------------------------------
>
>                 Key: HDFS-9890
>                 URL: https://issues.apache.org/jira/browse/HDFS-9890
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: Stephen
>         Attachments: HDFS-9890.HDFS-8707.000.patch
>
>
> I propose adding a test suite to simulate various network issues/failures in order to
get good test coverage on some of the retry paths that aren't easy to hit in mock unit tests.
> At the moment the only things that hit the retry paths are the gmock unit tests.  The
gmock are only as good as their mock implementations which do a great job of simulating protocol
correctness but not more complex interactions.  They also can't really simulate the types
of lock contention and subtle memory stomps that show up while doing hundreds or thousands
of concurrent reads.   We should add a new minidfscluster test that focuses on heavy read/seek
load and then randomly convert error codes returned by network functions into errors.
> List of things to simulate(while heavily loaded), roughly in order of how badly I think
they need to be tested at the moment:
> -Rpc connection disconnect
> -Rpc connection slowed down enough to cause a timeout and trigger retry
> -DN connection disconnect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message