Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6A921200CC6 for ; Mon, 12 Jun 2017 10:12:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6930E160BD6; Mon, 12 Jun 2017 08:12:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A4656160BDE for ; Mon, 12 Jun 2017 10:12:04 +0200 (CEST) Received: (qmail 90084 invoked by uid 500); 12 Jun 2017 08:12:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 90050 invoked by uid 99); 12 Jun 2017 08:12:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jun 2017 08:12:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A4F7FC0A27 for ; Mon, 12 Jun 2017 08:12:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id g6zeDSFkh6DR for ; Mon, 12 Jun 2017 08:12:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D5EFC5FBE5 for ; Mon, 12 Jun 2017 08:12:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 62E7EE069F for ; Mon, 12 Jun 2017 08:12:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2388521E0D for ; Mon, 12 Jun 2017 08:12:00 +0000 (UTC) Date: Mon, 12 Jun 2017 08:12:00 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-11963) Ozone: Documentation: Add getting started page MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 12 Jun 2017 08:12:05 -0000 [ https://issues.apache.org/jira/browse/HDFS-11963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046311#comment-16046311 ] Weiwei Yang commented on HDFS-11963: ------------------------------------ Hi [~anu] Thanks for writing this up, it looks really good. I did a quick look and few comments bq. +| ozone.scm.names | SCM server name | Hostname or IP address of SCM. Generally same as namenode machine. | do we need to mention this could have port as well in case user wants to customized port for SCMs? bq. +Ozone is designed to run concurrently with HDFS. The simplest way to start +HDFS is to run `start-dfs.sh` from the `$HADOOP/sbin/start-dfs.sh`. Can we link this to HDFS [cluster setup guide|http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/ClusterSetup.html]? In your document, there is no mention of ksm node configuration, e.g {{ozone.ksm.address}}. But I guess we need to expose this in the setup section? We need to add all configurable entries into ozone-default.xml and make it available for users. Currently I don't think ozone-default.xml is up-to-date. bq. +`--root` option allows the command to be executed as user `hdfs` which is an +admin in the cluster. It looks like we are hard coding admin user as "hdfs", we need to correct this because admin user is the user who starts ozone, that could be any user. Thanks > Ozone: Documentation: Add getting started page > ---------------------------------------------- > > Key: HDFS-11963 > URL: https://issues.apache.org/jira/browse/HDFS-11963 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Anu Engineer > Assignee: Anu Engineer > Attachments: HDFS-11963-HDFS-7240.001.patch, HDFS-11963-HDFS-7240.002.patch, Screen Shot 2017-06-11 at 12.11.06 AM.png, Screen Shot 2017-06-11 at 12.11.19 AM.png, Screen Shot 2017-06-11 at 12.11.32 AM.png > > > We need to add the Ozone section to hadoop documentation and also a section on how to get started, that is what are configuration settings needed to start running ozone. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org