[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831213#comment-16831213
]
Eric Yang commented on HDDS-1458:
---------------------------------
[~elek] Patch 002 move blockade tests from dist to
fault-injection-test/network-tests. It also created a setup for disk based
tests. There is a problem with Ozone docker image is that it mounts ozone
tarball in expanded form from dist/target directory. This prevents
integration-test to reiterate on the same ozone binaries. I made a fix for
docker image to build as a separate submodule using maven-assembly instead of
dist-tar-stitching. Dist-tar-stitching was invented to fix symlink support in
tarball. However, it introduced a regression in maven dependency. Maven is
unable to reference ozone tarball for docker image build. I verified that
ozone tarball does not require symlink, therefore, switching to maven-assembly
can produce Docker Ozone image in maven build more efficiently.
> 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
> Attachments: HDDS-1458.001.patch, HDDS-1458.002.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
