Ozone without replication

[gigem]

I am trying to evaluate Ozone for use with Hive. Because of IT decisions, our cluster runs on VMs with a SAN using RAID. Consquently, we don't believe we need any replication from Ozone. Unfortunately, I can't seem to get any working configuration without needing extra nodes. Here is an example error:

2023-11-08 16:19:34,639 [RatisPipelineUtilsThread - 0] ERROR org.apache.hadoop.hdds.scm.SCMCommonPlacementPolicy: Unable to find enough nodes that meet the space requirement of 1073741824 bytes for metadata and 5368709120 bytes for data in healthy node set. Required 3. Found 1.

I've tried with the plain, docker-compose example (with --scale=1 and --scale=3) and also with an "onprem" installation using 1 node. I've tried setting the default, replication type to STAND_ALONE and also with creating bickets with replication type set to RATIS and replication factor set to 1. Strangely, I'm not allowed to create buckets with replication type set to STAND_ALONE.

I can't help but feel I'm missing something fundamental. Can someone please guide me on how to configure Ozone for use without replication. If that's not possible, how to do it with minimal waste.

[adoroszlai]

@gigem Can you please share which version of Ozone you are using?

[DaveTeng0]

hm, there'll be a 1.4.0 release around December!

[adoroszlai]

For dev testing and POC purposes I think latest commit from master is OK, with some caveats (known issues). See details in on-going discussion on dev@ mailing list about next major release.

[gigem]

I've got about 1 or 2 weeks of POC testing left so a December release should work. I have a couple more, hopefully quick questions.

• How well does fuse-dfs (or similar) work with Ozone? In a few cases with non-S3/HDFS aware applications, we use a fuse mount to check file existance and copy data out.
• Is there a convenient way to copy/mirror data from S3 to Ozone? We have serveral TBs of data we will want to move.

[adoroszlai]

@gigem I would like to suggest asking each of these questions in a separate discussion for better visibility (both to people who answer and those who are looking for answers).

[gigem]

@adoroszlai, done.

[DaveTeng0]

thanks @adoroszlai for the answer, that solves the same issue I got.