Tuning Ozone for faster deletion performance

Learn how to use the Ozone configuration properties to tune Ozone for faster deletion performance under various workload conditions.

For deletion performance optimization and to overcome known issues, Cloudera recommends the following additional configurations based on different workload conditions:

Speeding up deeply nested directory deletion

If you are experiencing slowness specifically when deleting deeply nested directory structures or a large number of directories, update the following configurations in the OzoneManager (OM):

ozone.thread.number.dir.deletion = 30
ozone.directory.deleting.service.interval = 30s

Improving general (system-wide) deletion speed

When you observe general deletion slowness across the cluster or require faster overall delete throughput, update the following parameters in their respective services:

OzoneManager (OM) configurations

ozone.block.deleting.service.interval = 30s
ozone.key.deleting.limit.per.task = 200000
ozone.directory.deleting.service.interval = 30s

StorageContainerManager (SCM) configurations
```
hdds.scm.block.deletion.per-interval.max = 2000000
```

DataNode (DN) configurations

hdds.datanode.block.deleting.limit.per.interval = 50000
ozone.block.deleting.service.workers = 30
hdds.datanode.block.deleting.service.interval = 30s