Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 30 Apr 2017 06:52:04 +0000 (UTC)
From: "Weiwei Yang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13067979.1493534990000.86901.1493535124039@Atlassian.JIRA>
In-Reply-To: <JIRA.13067979.1493534990000@Atlassian.JIRA>
References: <JIRA.13067979.1493534990000@Atlassian.JIRA> <JIRA.13067979.1493534990788@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-11725) Ozone: Revise create container CLI
 specification and implementation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 30 Apr 2017 06:52:09 -0000


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

Weiwei Yang commented on HDFS-11725:
------------------------------------

Hi [~anu], please let me know how to update the design doc in HDFS-11470. Maybe we could add this doc to an online editor? Thanks.

> 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
>
> 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
(v6.3.15#6346)

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