[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831742#comment-16831742
]
Eric Badger commented on HDDS-1458:
-----------------------------------
bq. Jonathan Eagles Eric Badger, please speak up if you have concerns to rename
docker profile to dist profile.
As I commented in YARN-7129, I am against adding mandatory Docker image builds
to the default Hadoop build process. The community came to this same consensus
via [this mailing list thread|
https://lists.apache.org/thread.html/c63f404bc44f8f249cbc98ee3f6633384900d07e2308008fe4620150@%3Ccommon-dev.hadoop.apache.org%3E].
However, I am not an HDDS developer and do not have proper insight into HDDS
development. So I can only give my thoughts on this from a YARN perspective.
Maybe this is a great idea for HDDS, maybe it's not. Since I don't know
anything about HDDS, I can't really give you an opinion. But I think that it
definitely warrants getting more eyes and reviews on this from the HDDS
community
> 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]
