Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 27 Sep 2017 18:51:01 +0000 (UTC)
From: "Chen Liang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13102381.1505422911000.218317.1506538261043@Atlassian.JIRA>
In-Reply-To: <JIRA.13102381.1505422911000@Atlassian.JIRA>
References: <JIRA.13102381.1505422911000@Atlassian.JIRA> <JIRA.13102381.1505422911819@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12454) Ozone : the sample ozone-site.xml
 in OzoneGettingStarted does not work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 27 Sep 2017 18:51:07 -0000


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

Chen Liang commented on HDFS-12454:
-----------------------------------

[~anu]
bq. re-confirm that we cannot have a DNS:PORT 
By DNS, did you mean hostname? I have only tested the config in local one machine environment, something like localhost:port did work for me. I haven't tested this config for multi-machine setup, I don't see any reason why hostname won't work for multi-node though. Earlier there was a comment
bq. I think we do need ozone.ksm.address, let user explicitly set this property helps them to understand the primitive services' location. And this should be an address, not a hostname.
[~cheersyang] is there a particular reason why you prefer IP address rather than hostname? does hostname work here at all for multi-node?

> Ozone : the sample ozone-site.xml in OzoneGettingStarted does not work
> ----------------------------------------------------------------------
>
>                 Key: HDFS-12454
>                 URL: https://issues.apache.org/jira/browse/HDFS-12454
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Chen Liang
>            Assignee: Chen Liang
>            Priority: Blocker
>              Labels: ozoneMerge
>             Fix For: HDFS-7240
>
>         Attachments: HDFS-12454-HDFS-7240.001.patch, HDFS-12454-HDFS-7240.002.patch, HDFS-12454-HDFS-7240.003.patch, HDFS-12454-HDFS-7240.004.patch, HDFS-12454-HDFS-7240.005.patch
>
>
> In OzoneGettingStarted.md there is a sample ozone-site.xml file. But there are a few issues with it.
> 1.
> {code}
>         <property>
>           <name>ozone.scm.block.client.address</name>
>           <value>scm.hadoop.apache.org</value>
>         </property>
>          <property>
>             <name>ozone.ksm.address</name>
>             <value>ksm.hadoop.apache.org</value>
>           </property>
> {code}
> The value should be an address instead.
> 2.
> {{datanode.ObjectStoreHandler.<init>(ObjectStoreHandler.java:103)}} requires {{ozone.scm.client.address}} to be set, which is missing from this sample file. Missing this config will seem to cause failure on starting datanode.
> 3.
> {code}
>         <property>
>           <name>ozone.scm.names</name>
>           <value>scm.hadoop.apache.org</value>
>         </property>
> {code}
> This value did not make much sense to, I found the comment in {{ScmConfigKeys}} that says
> {code}
> // ozone.scm.names key is a set of DNS | DNS:PORT | IP Address | IP:PORT.
> // Written as a comma separated string. e.g. scm1, scm2:8020, 7.7.7.7:7777
> {code}
> So maybe we should write something like scm1 as value here.
> 4. I'm not entirely sure about this, but [here|https://wiki.apache.org/hadoop/Ozone#Configuration] it says 
> {code}
> <property>
>     <name>ozone.handler.type</name>
>     <value>local</value>
>   </property>
> {code}
> is also part of minimum setting, do we need to add this [~anu]?


--
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