[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841818#comment-16841818
]
Eric Yang commented on HDDS-1458:
---------------------------------
[~anu] {quote}Sorry this makes no sense. If you want simulate disk failures, it
is easier with a container based approach and it really does not matter where
the containers run. {quote}
Some disk tests can not be simulated without distributing IO to multiple disks.
A single node will have all containers running from the same disk. It is
harder to simulate isolated fault injection to scm disk when all containers
share the same physical disk IMHO, but the conversation is digressing from
layout of current tool chain.
I will make the new tests in the tarball when tests are written. I don't have
a way to do that in this patch because this patch only setup the module layout.
In the follow up patch, I will worry about race condition between compiling
test code and packaging the test code in tarball. This means junit based java
test can not be used. I am less thrill to look at test reports on terminal
console than looking them through Jenkins, but tests can be part of tarball.
Maven and Robot Test framework can do exactly the same thing for keyword based
tests. I don't know why we choose to do both when Maven is already used daily.
I am not going to interrupt the plan and will make the tests to support both
maven and robots framework. Does this sound fair?
> Create a maven profile to run fault injection tests
> ---------------------------------------------------
>
> Key: HDDS-1458
> URL: https://issues.apache.org/jira/browse/HDDS-1458
> Project: Hadoop Distributed Data Store
> Issue Type: Test
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.1
>
> Attachments: HDDS-1458.001.patch, HDDS-1458.002.patch,
> HDDS-1458.003.patch, HDDS-1458.004.patch, HDDS-1458.005.patch,
> HDDS-1458.006.patch, HDDS-1458.007.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Some fault injection tests have been written using blockade. It would be
> nice to have ability to start docker compose and exercise the blockade test
> cases against Ozone docker containers, and generate reports. This is
> optional integration tests to catch race conditions and fault tolerance
> defects.
> We can introduce a profile with id: it (short for integration tests). This
> will launch docker compose via maven-exec-plugin and run blockade to simulate
> container failures and timeout.
> Usage command:
> {code}
> mvn clean verify -Pit
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
