[
https://issues.apache.org/jira/browse/HDDS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881619#comment-16881619
]
Arpit Agarwal commented on HDDS-1554:
-------------------------------------
Hi [~eyang], I tried running the tests with {{mvn verify -Pit}} under
_hadoop-ozone/fault-injection-test/disk-tests_.
It failed with the following error:
{code}
[ERROR] services.datanode1.user contains an invalid type, it should be a string
[ERROR] services.datanode2.user contains an invalid type, it should be a string
[ERROR] services.datanode3.user contains an invalid type, it should be a string
[ERROR] services.om.user contains an invalid type, it should be a string
[ERROR] services.scm.user contains an invalid type, it should be a string
{code}
I think the docker-compose.yaml files should wrap {{${UID}:${GID}}} in quotes.
Another issue I ran into: Since the docker inline build with {{-Ddocker-build}}
generates the image with {{${user.name}/ozone}}, should we use the same in the
docker-compose files instead of {{apache/ozone}}?
There is quite a bit of duplication of the configuration files and YAML files.
Do you think there is a way to reduce the duplication?
Still reviewing the java test cases.
> Create disk tests for fault injection test
> ------------------------------------------
>
> Key: HDDS-1554
> URL: https://issues.apache.org/jira/browse/HDDS-1554
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-1554.001.patch, HDDS-1554.002.patch,
> HDDS-1554.003.patch, HDDS-1554.004.patch, HDDS-1554.005.patch,
> HDDS-1554.006.patch, HDDS-1554.007.patch, HDDS-1554.008.patch,
> HDDS-1554.009.patch, HDDS-1554.010.patch, HDDS-1554.011.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The current plan for fault injection disk tests are:
> # Scenario 1 - Read/Write test
> ## Run docker-compose to bring up a cluster
> ## Initialize scm and om
> ## Upload data to Ozone cluster
> ## Verify data is correct
> ## Shutdown cluster
> # Scenario 2 - Read/Only test
> ## Repeat Scenario 1
> ## Mount data disk as read only
> ## Try to write data to Ozone cluster
> ## Validate error message is correct
> ## Shutdown cluster
> # Scenario 3 - Corruption test
> ## Repeat Scenario 2
> ## Shutdown cluster
> ## Modify data disk data
> ## Restart cluster
> ## Validate error message for read from corrupted data
> ## Validate error message for write to corrupted volume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
