[
https://issues.apache.org/jira/browse/HDFS-12454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168288#comment-16168288
]
Chen Liang commented on HDFS-12454:
-----------------------------------
Thanks [~cheersyang] and [~anu] for the comments!
bq. I think we do need ozone.ksm.address
This is actually a good catch, as just I realized that many ozone ops need the
address, for example {{hdfs oz -listtBucket http://localhost:9864/hive}}, so
the user better know it is 'localhost:9864' to use by having explicitly put it
in the config.
But another thing I noticed is that all the commands in the docs seem to use
port 9864 as ksm port. But in {{KSMConfigKeys}}, the default port seems to be
9874. And in fact seems 9864 is a used port by hdfs i.e. {{DFSConfigKeys}} has
{{DFS_DATANODE_HTTP_DEFAULT_PORT = 9864;}}. So it appears to me that if we run
a datanode along with KSM on the same machine and ozone config uses 9864, there
will likely be a collision on this port...
So I'm going to update the docs to have the sample config, as well as all the
sample commands in the docs, use 9874 for ksm port instead.
> 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
> Attachments: HDFS-12454-HDFS-7240.001.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: [email protected]
For additional commands, e-mail: [email protected]
