Thank you for update:)
The same issue when i configed the parameters you give me.
[root@node219 hadoop]# cat ozone-site.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configuration>
<property>
<name>ozone.om.address</name>
<value>192.168.21.219</value>
<tag>OM, REQUIRED</tag>
<description>
The address of the Ozone OM service. This allows clients to discover
the address of the OM.
</description>
</property>
<property>
<name>ozone.metadata.dirs</name>
<value>/data01/ozone</value>
<tag>OZONE, OM, SCM, CONTAINER, STORAGE, REQUIRED</tag>
<description>
This setting is the fallback location for SCM, OM, Recon and DataNodes
to store their metadata. This setting may be used only in test/PoC
clusters to simplify configuration.
For production clusters or any time you care about performance, it is
recommended that ozone.om.db.dirs, ozone.scm.db.dirs and
dfs.container.ratis.datanode.storage.dir be configured separately.
</description>
</property>
<property>
<name>ozone.scm.client.address</name>
<value>192.168.21.219</value>
<tag>OZONE, SCM, REQUIRED</tag>
<description>
The address of the Ozone SCM client service. This is a required setting.
It is a string in the host:port format. The port number is optional
and defaults to 9860.
</description>
</property>
<property>
<name>ozone.scm.names</name>
<value>192.168.21.219</value>
<tag>OZONE, REQUIRED</tag>
<description>
The value of this property 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.
This property allows datanodes to discover where SCM is, so that
datanodes can send heartbeat to SCM.
</description>
</property>
<property>
<name>hdds.datanode.dir</name>
<value>/data01/ozone/dn01</value>
<tag>OZONE, CONTAINER, STORAGE, MANAGEMENT</tag>
<description>Determines where on the local filesystem HDDS data will be
stored. Defaults to dfs.datanode.data.dir if not specified.
The directories should be tagged with corresponding storage
types
([SSD]/[DISK]/[ARCHIVE]/[RAM_DISK]) for storage policies. The
default
storage type will be DISK if the directory does not have a
storage type
tagged explicitly.
</description>
</property>
<property>
<name>ozone.scm.heartbeat.rpc-timeout</name>
<value>30s</value>
<tag>OZONE, MANAGEMENT</tag>
<description>
Timeout value for the RPC from Datanode to SCM.
</description>
</property>
<property>
<name>ozone.scm.heartbeat.rpc-retry-interval</name>
<value>60s</value>
<tag>OZONE, MANAGEMENT</tag>
<description>
Retry interval for the RPC from Datanode to SCM.
Make sure rpc-retry-count * (rpc-timeout + rpc-retry-interval)
is less than hdds.heartbeat.interval.
</description>
</property>
<property>
<name>ozone.scm.pipeline.creation.auto.factor.one</name>
<value>true</value>
<tag>OZONE, SCM, PIPELINE</tag>
<description>
If enabled, SCM will auto create RATIS factor ONE pipeline.
</description>
</property>
<property>
<name>ozone.scm.datanode.pipeline.limit</name>
<value>5</value>
<tag>OZONE, SCM, PIPELINE</tag>
<description>Max number of pipelines per datanode can be engaged in.
Setting the value to 0 means the pipeline limit per dn will be determined
by the no of metadata volumes reported per dn.
</description>
</property>
</configuration>
此致，敬礼！
董延辉
电话：13633860082
Email:dongyan...@nnct-nsn.com
From: Sammi Chen
Date: 2021-04-07 10:22
To: dev
CC: dongyanhui
Subject: Re: I have a problem with Ozone 1.0.0
Hey dongyanhui，
From the " ozone admin datanode list " output, we can see that there is only
one THREE factor pipeline, which involves three datanode 219, 220, 225. I
guess your data requires three replicas, so that your data is written to these
three datanodes.
To tuning the cluster, you can try,
1. controls whether factor one pipeline should be created. If you don't need
to write one replica data, you can turn this off .
<property>
<name>ozone.scm.pipeline.creation.auto.factor.one</name>
<value>true</value>
<tag>OZONE, SCM, PIPELINE</tag>
<description>
If enabled, SCM will auto create RATIS factor ONE pipeline.
</description>
</property>
2. controls how many pipelines can a DN have. You can increase this number,
say 5, if you have more than 5 DN disks configured.
<property>
<name>ozone.scm.datanode.pipeline.limit</name>
<value>2</value>
<tag>OZONE, SCM, PIPELINE</tag>
<description>Max number of pipelines per datanode can be engaged in.
Setting the value to 0 means the pipeline limit per dn will be determined
by the no of metadata volumes reported per dn.
</description>
</property>
Regards,
Sammi
On Tue, Apr 6, 2021 at 8:41 PM Elek, Marton <e...@apache.org> wrote:
-------- Forwarded Message --------
Subject: I have a problem with Ozone 1.0.0
Date: Tue, 6 Apr 2021 12:16:57 +0800
From: dongyan...@nnct-nsn.com <dongyan...@nnct-nsn.com>
To: issues <iss...@ozone.apache.org>
Hi,Support!
1：I have installed the Ozone 1.0.1 sucessfully with 5 datanodes.
[root@node221 logs]# ozone admin datanode list
Datanode: 3e970fc5-c0a3-46c0-812f-9743ea879fce
(/default-rack/192.168.21.226/node226.cluster1.com/1 pipelines)
Related pipelines:
9004918c-6026-49a4-a024-5477cef464ab/ONE/RATIS/OPEN/Leader
Datanode: e18fd3bf-009f-4d45-a358-4a8efdd4ef30
(/default-rack/192.168.21.221/node221.cluster1.com/1 pipelines)
Related pipelines:
e75d2266-2aa1-49ad-ac16-0ed6895c9550/ONE/RATIS/OPEN/Leader
Datanode: d07c8e6b-566f-4b5d-a21c-648a053c5b45
(/default-rack/192.168.21.220/node220.cluster1.com/2 pipelines)
Related pipelines:
5e8f70e1-0939-4ff7-9da7-8d65524c330d/THREE/RATIS/OPEN/Follower
e000dffa-8a70-4833-9a9b-eb13e367e7dd/ONE/RATIS/OPEN/Leader
Datanode: 951aef66-9b85-4942-a218-a25f758f192d
(/default-rack/192.168.21.219/node219.cluster1.com/2 pipelines)
Related pipelines:
5e8f70e1-0939-4ff7-9da7-8d65524c330d/THREE/RATIS/OPEN/Follower
54d792ec-5117-4678-951e-e22ca99bf5e5/ONE/RATIS/OPEN/Leader
Datanode: f3e011c6-e08e-4aba-8b43-dc4bfa87f752
(/default-rack/192.168.21.225/node225.cluster1.com/2 pipelines)
Related pipelines:
3f6d26d2-52c2-41f9-8e8f-ede7c111074f/ONE/RATIS/OPEN/Leader
5e8f70e1-0939-4ff7-9da7-8d65524c330d/THREE/RATIS/OPEN/Leader
2：I have a problem with Ozone 1.0.0 as bellow:
The dns can increase more than 3 nodes, but The data can upload to 3
datanodes only,*is their licensing restrictions?*
[root@node219 hadoop]# du -sh /data01/ozone/*
4.0K /data01/ozone/datanode.id
4.0K /data01/ozone/db.checkpoints
7.4G /data01/ozone/dn01
7.2G /data01/ozone/dn02
7.7G /data01/ozone/dn03
12K /data01/ozone/om
146M /data01/ozone/om.db
4.0K /data01/ozone/omMetrics
6.6M /data01/ozone/ratis
12K /data01/ozone/scm
146M /data01/ozone/scm.db
[root@node220 ~]# du -sh /data01/ozone/*
4.0K /data01/ozone/datanode.id
7.5G /data01/ozone/dn01
7.3G /data01/ozone/dn02
7.7G /data01/ozone/dn03
6.7M /data01/ozone/ratis
[root@node221 logs]# du -sh /data01/ozone/*
4.0K /data01/ozone/datanode.id
20K /data01/ozone/dn01
20K /data01/ozone/dn02
20K /data01/ozone/dn03
48K /data01/ozone/ratis
[root@node225 ~]# du -sh /data01/ozone/*
4.0K /data01/ozone/datanode.id
7.7G /data01/ozone/dn01
7.3G /data01/ozone/dn02
7.9G /data01/ozone/dn03
6.7M /data01/ozone/ratis
[root@node226 ~]# du -sh /data01/ozone/*
4.0K /data01/ozone/datanode.id
16K /data01/ozone/dn01
16K /data01/ozone/dn02
16K /data01/ozone/dn03
44K /data01/ozone/ratis
3: The ozone config as bellow:
[root@node219 hadoop]# cat ozone-site.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configuration>
<property>
<name>ozone.om.address</name>
<value>192.168.21.219</value>
<tag>OM, REQUIRED</tag>
<description>
The address of the Ozone OM service. This allows clients to discover
the address of the OM.
</description>
</property>
<property>
<name>ozone.metadata.dirs</name>
<value>/data01/ozone</value>
<tag>OZONE, OM, SCM, CONTAINER, STORAGE, REQUIRED</tag>
<description>
This setting is the fallback location for SCM, OM, Recon and DataNodes
to store their metadata. This setting may be used only in test/PoC
clusters to simplify configuration.
For production clusters or any time you care about performance, it is
recommended that ozone.om.db.dirs, ozone.scm.db.dirs and
dfs.container.ratis.datanode.storage.dir be configured separately.
</description>
</property>
<property>
<name>ozone.scm.client.address</name>
<value>192.168.21.219</value>
<tag>OZONE, SCM, REQUIRED</tag>
<description>
The address of the Ozone SCM client service. This is a required setting.
It is a string in the host:port format. The port number is optional
and defaults to 9860.
</description>
</property>
<property>
<name>ozone.scm.names</name>
<value>192.168.21.219</value>
<tag>OZONE, REQUIRED</tag>
<description>
The value of this property 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.
This property allows datanodes to discover where SCM is, so that
datanodes can send heartbeat to SCM.
</description>
</property>
<property>
<name>hdds.datanode.dir</name>
<value>/data01/ozone/dn01,/data01/ozone/dn02,/data01/ozone/dn03</value>
<tag>OZONE, CONTAINER, STORAGE, MANAGEMENT</tag>
<description>Determines where on the local filesystem HDDS data will be
stored. Defaults to dfs.datanode.data.dir if not specified.
The directories should be tagged with corresponding storage
types
([SSD]/[DISK]/[ARCHIVE]/[RAM_DISK]) for storage policies. The
default
storage type will be DISK if the directory does not have a
storage type
tagged explicitly.
</description>
</property>
</configuration>
4: ozone version
[root@node221 logs]# ozone version
//////////////
////////////////////
//////// ////////////////
////// ////////////////
///// //////////////// /
///// //////// ///
//// //////// /////
///// ////////////////
///// //////////////// //
//// /////////////// /////
///// /////////////// ////
///// ////// /////
////// ////// /////
/////////// ////////
////// ////////////
/// //////////
/ 1.0.0(Denali)
Source code repository Unknown -r Unknown
Compiled by root on 2021-04-02T09:53Z
Compiled with protoc 2.5.0
From source with checksum 49ea4ac8358b9bfbdcda09565e1fcd8
Using HDDS 1.0.0
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
