[
https://issues.apache.org/jira/browse/HDFS-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101029#comment-14101029
]
Brandon Li commented on HDFS-5135:
----------------------------------
[~jayunit100], thanks for pointing us to the bigtop test which looks very nice.
Here we see two kinds of e2e tests with each covering different test cases:
1. send/receive request from TCP/UDP client with manually crafted RPC requests
and can have fine control of the sequence of requests. The RPC request could
have any right or wrong format combination to test server's reaction. The
requests sequence can also be made to test regression of some specific bugs.
2. do operations from shell. It's the real e2e test and very convenient to
invoke the request from real NFS clients. Moreover, running the same test on
different platforms (or even different linux releases), the NFS server might
get different sequence of requests(e.g., due to the linux kernel changes).
I was previously talking about the first e2e tests. But after read Jay's
comments, I think we need both kinds of tests in NFS project because hadoop
developers may not always run bigtop tests to validate their code change.
We could move this JIRA out from HDFS-4750 and promote it to be an umbrella
JIRA to better manage the effort. comments?
> Create a test framework to enable NFS end to end unit test
> ----------------------------------------------------------
>
> Key: HDFS-5135
> URL: https://issues.apache.org/jira/browse/HDFS-5135
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: nfs
> Affects Versions: 2.2.0
> Reporter: Brandon Li
> Assignee: Zhe Zhang
>
> Currently, we have to manually start portmap and nfs3 processes to test patch
> and new functionalities. This JIRA is to track the effort to introduce a test
> framework to NFS unit test without starting standalone nfs3 processes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
