Single Node Development Cluster
This is the traditional way to start a development cluster from source code. Once the package is built, you can start Ozone services by going to the hadoop-ozone/dist/target/ozone-*/ directory. Your Unix shell should expand the '*' wildcard to the correct Ozone version number.
Configuration
Save the minimal snippet to hadoop-ozone/dist/target/ozone-*/etc/hadoop/ozone-site.xml in the compiled distribution.
| Code Block |
|---|
|
<configuration>
<properties>
<property><name>ozone.scm.datanode.id.dir</name><value>/tmp/ozone/data</value></property>
<property><name>ozone.replication</name><value>1</value></property>
<property><name>ozone.metadata.dirs</name><value>/tmp/ozone/data/metadata</value></property>
<property><name>ozone.scm.names</name><value>localhost</value></property>
<property><name>ozone.om.address</name><value>localhost</value></property>
<property><name>ozone.scm.block.client.address</name><value>localhost</value></property>
<property><name>ozone.scm.client.address</name><value>localhost</value></property>
<property><name>ozone.scm.db.dirs</name><value>/tmp/ozone/scm/db</value></property>
<property><name>ozone.scm.ha.ratis.storage.dir</name><value>/tmp/ozone/scm/ratis</value></property>
<property><name>ozone.om.db.dirs</name><value>/tmp/ozone/om/db</value></property>
<property><name>ozone.om.ratis.storage.dir</name><value>/tmp/ozone/om/ratis</value></property>
<property><name>dfs.container.ratis.datanode.storage.dir</name><value>/tmp/ozone/datanode/ratis</value></property>
<property><name>hdds.datanode.dir</name><value>/tmp/ozone/datanode/data</value></property>
</properties>
</configuration> |
Start Services
To start ozone, you need to start SCM, OzoneManager and DataNode. In pseudo-cluster mode, all services will be started on localhost.
Note : jps (use this command to check if all the daemons are up and running or not)
| Code Block |
|---|
|
cd ../../ (move up two levels in the directory hierarchy to hadoop-ozone/dist/target/ozone-*/)
bin/ozone scm --init
bin/ozone --daemon start scm
bin/ozone om --init
bin/ozone --daemon start om
bin/ozone --daemon start datanode |
Run Ozone Commands
Once you have ozone running you can use these Ozone shell commands to create a volume, bucket and keys. E.g.
| Code Block |
|---|
|
bin/ozone sh volume create /vol1
bin/ozone sh bucket create /vol1/bucket1
dd if=/dev/zero of=/tmp/myfile bs=1024 count=1
bin/ozone sh key put -t=RATIS -r=ONE /vol1/bucket1/key1 /tmp/myfile
bin/ozone sh key list /vol1/bucket1 |
Note: specify replication type (-t) and replication factor (-r) to one for a single node cluster.
Stop Services
| Code Block |
|---|
|
bin/ozone --daemon stop om
bin/ozone --daemon stop scm
bin/ozone --daemon stop datanode |
Clean up your Dev Environment (Optional)
Remove the following directories to wipe the Ozone pseudo-cluster state. This will also delete all user data (volumes/buckets/keys) you added to the pseudo-cluster.
| Code Block |
|---|
|
rm -fr /tmp/ozone
rm -fr /tmp/hadoop-${USER}* |
| Info |
|---|
Note: This will also wipe state for any running HDFS services.
|
Add more content to complete your Multi-Page Journey
| Progress Bar Container |
|---|
|
| Progress Bar - Hyperlink Step |
|---|
| title | Step1Evaluate Ozone |
|---|
| url | Evaluate Try out Ozone |
|---|
|
| Progress Bar - Hyperlink Step |
|---|
| title | Step2Running via DockerHub |
|---|
| url | Running via DockerHub |
|---|
|
| Progress Bar - Hyperlink Step |
|---|
| title | Step3Running via Apache Release |
|---|
| url | Running via Apache Release |
|---|
|
| Progress Bar - Hyperlink Step |
|---|
| title | Step4 | url | Downloading Sources |
|---|
| | Progress Bar - Hyperlink Step |
|---|
| title | Step5 |
|---|
| url | Building Downloading Sources |
|---|
|
| Progress Bar - Hyperlink Step |
|---|
| title | Step6Single Node Deployment |
|---|
| url | Single Node Deployment |
|---|
|
| Progress Bar - Hyperlink Step |
|---|
| title | Step7Multi Node Ozone Cluster |
|---|
| url | Multi Node Ozone Cluster |
|---|
|
|
...