[
https://issues.apache.org/jira/browse/HDFS-12469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182017#comment-16182017
]
Anu Engineer commented on HDFS-12469:
-------------------------------------
I was able to run Corona from inside one of the containers. I am going to
commit this now.
{noformat}
***************************************************
Number of Volumes created: 1
Number of Buckets created: 10
Number of Keys added: 100
Time spent in volume creation: 00:00:00:473
Time spent in bucket creation: 00:00:00:31
Time spent in key creation: 00:00:00:279
Time spent in writing keys: 00:00:00:84
Total bytes written: 1024000
Total number of writes validated: 100
Writes validated: 100.0 %
Successful validation: 100
Unsuccessful validation: 0
Total Execution time: 00:00:06
***************************************************
{noformat}
Also one of the changes that I committed changed the a key name. So I have
fixed while committing.
OZONE-SITE.XML_ozone.metadata.dirs=/tmp/metadata This is the new key name.
> Ozone: Create docker-compose definition to easily test real clusters
> --------------------------------------------------------------------
>
> Key: HDFS-12469
> URL: https://issues.apache.org/jira/browse/HDFS-12469
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Labels: OzonePostMerge
> Fix For: HDFS-7240
>
> Attachments: HDFS-12469-HDFS-7240.001.patch,
> HDFS-12469-HDFS-7240.WIP1.patch, HDFS-12469-HDFS-7240.WIP2.patch
>
>
> The goal here is to create a docker-compose definition for ozone
> pseudo-cluster with docker (one component per container).
> Ideally after a full build the ozone cluster could be started easily with
> after a simple docker-compose up command.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
