hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11725) Ozone: Revise create container CLI specification and implementation
Date Thu, 26 Apr 2018 21:50:07 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455046#comment-16455046

Hudson commented on HDFS-11725:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14070 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14070/])
HDFS-11725. Ozone: Revise create container CLI specification and (omalley: rev 3158f479d3b7d06783e6d9c27fd677faf05a9f0d)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/ozone/scm/TestSCMCli.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/scm/cli/container/CreateContainerHandler.java

> Ozone: Revise create container CLI specification and implementation
> -------------------------------------------------------------------
>                 Key: HDFS-11725
>                 URL: https://issues.apache.org/jira/browse/HDFS-11725
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
>         Attachments: HDFS-11725-HDFS-7240.001.patch
> Per [design doc|https://issues.apache.org/jira/secure/attachment/12861478/storage-container-manager-cli-v002.pdf]
in HDFS-11470
> {noformat}
> hdfs scm -container create -p <pipelineID>
> Notes : This command connects to SCM and creates a container. Once the container is created
in the SCM, the corresponding container is created at the appropriate datanode. Optional -p
allows the user to control which pipeline to use while creating this container, this is strictly
for debugging and testing.
> {noformat}
> it has 2 problems with this design, 1st it does support a container name but it is quite
useful for testing; 2nd it supports an optional option for pipeline, that is not quite necessary
right now given SCM handles the creation of the pipelines, we might want to support this later.
So proposed to revise the CLI to
> {code}
> hdfs scm -container create -c <containerName>
> {code}
> the {{-c}} option is *required*. Backend it does following steps
> # Given the container name, ask SCM where the container should be replicated to. This
returns a pipeline.
> # Communicate with each datanode in the pipeline to create the container.
> this jira is to track the work to update both the design doc as well as the implementation.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message