[
https://issues.apache.org/jira/browse/HDDS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877340#comment-16877340
]
Eric Yang commented on HDDS-1554:
---------------------------------
Patch 10 rebase to current trunk. The current usage command is:
{code}
mvn clean verify -Pit,docker-build
{code}
It does not work without docker-build parameter because the default docker
image name apache/ozone:0.5.0-SNAPSHOT doesn't exist. User can force to build
apache/pzone:0.5.0-SNAPSHOT with:
{code}
mvn clean verify -Ddocker.image=apache/ozone:0.5.0-SNAPSHOT -Pit,docker-build
{code}
[~elek] [~arp] I was unsuccessful in communicating for a better default docker
image name for docker-build profile in HDDS-1667. This is the reason that
docker-build profile needs to be passed even when user is not building docker
image.
Patch 10 version is to discuss if we are open to eliminate docker-build passing
by making the docker.image name default to apache/ozone:${project.version}
because snapshot are most likely locally built image. There is no point to
make further distinction between user and apache docker image name prefix when
docker version tag already make the distinction in my view. I am not sure if
you can agree to this point.
The current test cases is same in the issue description with exception that
Read-only test does not fully initialize metadata. I will update a new version
of read-only test to ensure metadata initialization is done before mark volume
as read-only.
> 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
>
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
