Ozone configuration parameters

hdds.prometheus.endpoint.enabled

Enables the Prometheus endpoint for HDDS

false

ozone.administrators

A comma-separated list of user principals who have administrator privileges in Ozone

om

ozone.administrators.groups

A comma-separated list of groups whose members have administrator privileges in Ozone

hadoop

ozone.replication

Default replication factor for data in Ozone. Higher values provide higher redundancy

3

ozone.service.id

Unique identifier for the Ozone service which is used for multi-cluster configurations

 — 

ozone.http.basedir

Base directory for the HTTP Jetty server to extract contents

/srv/ozone/meta/webserver

ozone.network.topology.aware.read

Defines whether the data is read from the closest pipeline

false

ozone.security.enabled

Defines whether secure connections are enabled for Ozone

false

hadoop.security.authentication

Authentication mechanism for Hadoop and Ozone

simple

ozone.security.http.kerberos.enabled

Defines whether Kerberos-based HTTP authentication is used for Ozone services

false

ozone.http.filter.initializers

HTTP filter initializer for Kerberos-based authentication

 — 

ozone.http.policy

Specifies the HTTP filter initializer for Kerberos-based authentication

HTTP_ONLY

hdds.grpc.tls.enabled

Defines whether TLS is enabled for HDDS GRPC server communication

false

ozone.https.client.need-auth

Specifies whether HTTPS clients need to authenticate using certificates

false

ssl.server.keystore.location

Path to the keystore file

 — 

ssl.server.keystore.password

Password for the keystore file

 — 

ssl.server.truststore.location

Path to the truststore

 — 

ssl.server.truststore.password

Password for the truststore

 — 

xasecure.audit.destination.solr.batch.filespool.dir

Spool directory path

/srv/ranger/ozone_plugin/audit_solr_spool

xasecure.audit.destination.solr.urls

A URL of the Solr server to store audit events. Leave this property value empty or set it to NONE when using ZooKeeper to connect to Solr

 — 

xasecure.audit.destination.solr.zookeepers

Specifies the ZooKeeper connection string for the Solr destination

 — 

xasecure.audit.destination.solr.force.use.inmemory.jaas.config

Whether to use in-memory JAAS configuration file to connect to Solr

 — 

xasecure.audit.is.enabled

Enables Ranger audit

true

xasecure.audit.jaas.Client.loginModuleControlFlag

Specifies whether the success of the module is required, requisite, sufficient, or optional

 — 

xasecure.audit.jaas.Client.loginModuleName

Name of the authenticator class

 — 

xasecure.audit.jaas.Client.option.keyTab

Name of the keytab file to get the principal’s secret key

 — 

xasecure.audit.jaas.Client.option.principal

Name of the principal to be used

 — 

xasecure.audit.jaas.Client.option.serviceName

Name of a user or a service for login

 — 

xasecure.audit.jaas.Client.option.storeKey

Set this to true if you want the keytab or the principal’s key to be stored in the subject’s private credentials

 — 

xasecure.audit.jaas.Client.option.useKeyTab

Set this to true if you want the module to get the principal’s key from the keytab

 — 

ranger.plugin.ozone.policy.rest.url

 — 

ranger.plugin.ozone.service.name

Name of the Ranger service containing policies for this Ozone instance

 — 

ranger.plugin.ozone.policy.cache.dir

Directory where Ranger policies are cached after a successful retrieval from the source

/srv/ranger/ozone/policycache

ranger.plugin.ozone.policy.pollIntervalMs

How often to poll for changes in policies in milliseconds

30000

ranger.plugin.ozone.policy.rest.client.connection.timeoutMs

Ozone plugin connection timeout in milliseconds

120000

ranger.plugin.ozone.policy.rest.client.read.timeoutMs

Ozone plugin read timeout in milliseconds

30000

ranger.plugin.ozone.policy.rest.ssl.config.file

Path to the RangerRestClient SSL config file for the Ozone plugin

/etc/ozone/conf/ranger-hbase-policymgr-ssl.xml

xasecure.policymgr.clientssl.keystore

Path to the keystore file used by Ranger

 — 

xasecure.policymgr.clientssl.keystore.credential.file

Path to the keystore credentials file

/etc/ozone/conf/ranger-ozone.jceks

xasecure.policymgr.clientssl.truststore.credential.file

Path to the truststore credentials file

/etc/ozone/conf/ranger-ozone.jceks

xasecure.policymgr.clientssl.truststore

Path to the truststore file used by Ranger

 — 

xasecure.policymgr.clientssl.keystore.password

Password to the keystore file

 — 

xasecure.policymgr.clientssl.truststore.password

Password to the truststore file

 — 

Encryption enable

Defines whether the credentials are encrypted

false

Credential provider path

Path to the credential provider for creating the .jceks files containing secret keys

jceks://file/etc/ozone/conf/ozone.jceks

Ranger plugin credential provider path

Path to the Ranger plugin credential provider

jceks://file/etc/ozone/conf/ranger-ozone.jceks

Custom jceks

Defines whether custom .jceks files located at the credential provider path (true) or auto-generated ones (false) are used

false

Password file name

Name of the password file in the classpath of the service if the password file is selected in the credstore options

ozone_credstore_pass

Custom ozone-site.xml

 — 

Custom ssl-server.xml.xml

 — 

Custom ranger-ozone-audit.xml

 — 

Custom ranger-ozone-security.xml

 — 

Custom ranger-ozone-policymgr-ssl.xml

 — 

hdds.datanode.http-address

HTTP address of the Datanode web interface

0.0.0.0:9882

hdds.datanode.https-address

HTTPS address of the Datanode web interface

0.0.0.0:9883

ozone.scm.datanode.id.dir

Path to the directory where the Datanode stores its unique identifier file

/srv/ozone/meta/node

hdds.datanode.dir

Determines, where on the local filesystem the Datanode should store its data. If multiple directories are specified, then data will be stored in all named directories, typically on different devices. The directories should be tagged with corresponding storage types (SSD/DISK/ARCHIVE/RAM_DISK). The default storage type will be DISK if the directory does not have a storage type tagged explicitly. Directories, that do not exist, will be created if the local filesystem permission allows

/srv/ozone/data:DISK

hdds.datanode.container.db.dir

Determines, where on the local filesystem the Datanode should store container database files. If multiple directories are specified, then data will be stored in all named directories, typically on different devices. The directories should be tagged with corresponding storage types (SSD/DISK/ARCHIVE/RAM_DISK). The default storage type will be DISK if the directory does not have a storage type tagged explicitly. Directories, that do not exist, will be created if the local filesystem permission allows

/srv/ozone/data/db:DISK

hdds.container.ratis.datanode.storage.dir

Path to the directory for storing Ratis logs for the Datanode

/srv/ozone/data/logs

hdds.container.ratis.enabled

Defines whether the Ratis for the Datanode is enabled to provide high availability and replication

true

hdds.container.ratis.datastream.enabled

Defines whether the DataStream is supported in Ratis for efficient data streaming between Datanodes

true

hdds.container.ratis.datastream.port

Port used for Ratis DataStream on the Datanode

9855

ozone.fs.datastream.enabled

Defines whether the data streaming over the filesystem for Ozone is enabled

true

ozone.container.cache.size

Size of the container cache for metadata and other frequently accessed data, in megabytes

8192

ozone.container.cache.lock.stripes

Number of lock stripes for container cache. It is used to manage concurrent access

8192

hdds.datanode.du.factory.classname

Defines the factory class for calculating disk usage on the Datanode

org.apache.hadoop.hdds.fs.DedicatedDiskSpaceUsageFactory

hdds.container.report.interval

Interval for the Datanode to send the container reports to Storage Container Manager

10m

hdds.container.ratis.leader.pending.bytes.limit

Limit for the pending bytes for the Ratis leader in a Datanode

2GB

ozone.recon.address

Address for connecting to the Recon server for the Datanode metrics and reports

{{ groups['ozone.ozone_recon'][0] | d('0.0.0.0') }}:9891

dfs.datanode.kerberos.principal

Datanode service Kerberos principal

 — 

dfs.datanode.kerberos.keytab.file

Path to the keytab file used by the Datanode daemon as its service principal to log in with

 — 

hdds.datanode.http.auth.type

Authentication mechanism for the Datanode HTTP server

 — 

hdds.datanode.http.auth.kerberos.principal

Datanode HTTP server service principal

 — 

hdds.datanode.http.auth.kerberos.keytab

Path to the keytab file used by the Datanode HTTP server as its service principal to log in with

 — 

Custom ozone-site.conf

 — 

Enable custom ulimits

Switch on the corresponding toggle button to specify resource limits (ulimits) for the current process. If you do not set these values, the default system settings are used. Ulimit settings are described in the table below

LimitCPU

A limit in seconds on the amount of CPU time that a process can consume

cpu time ( -t)

LimitFSIZE

Maximum size of files that a process can create, in 512-byte blocks

file size ( -f)

LimitDATA

Maximum size of a process’s data segment, in kilobytes

data seg size ( -d)

LimitSTACK

Maximum stack size allocated to a process, in kilobytes

stack size ( -s)

LimitCORE

Maximum size of a core dump file allowed for a process, in 512-byte blocks

core file size ( -c)

LimitRSS

The maximum amount of RAM memory (resident set size) that can be allocated to a process, in kilobytes

max memory size ( -m)

LimitNOFILE

Maximum number of open file descriptors allowed for the process

open files ( -n)

LimitAS

Maximum size of the process virtual memory (address space), in kilobytes

virtual memory ( -v)

LimitNPROC

Maximum number of processes

max user processes ( -u)

LimitMEMLOCK

Maximum memory size that can be locked for the process, in kilobytes. Memory locking ensures the memory is always in RAM and a swap file is not used

max locked memory ( -l)

LimitLOCKS

Maximum number of files locked by a process

file locks ( -x)

LimitSIGPENDING

Maximum number of signals that are pending for delivery to the calling thread

pending signals ( -i)

LimitMSGQUEUE

Maximum number of bytes in POSIX message queues. POSIX message queues allow processes to exchange data in the form of messages

POSIX message queues ( -q)

LimitNICE

Maximum NICE priority level that can be assigned to a process

scheduling priority ( -e)

LimitRTPRIO

Maximum real-time scheduling priority level

real-time priority ( -r)

LimitRTTIME

Maximum pipe buffer size, in 512-byte blocks

pipe size ( -p)

HTTPFS_CONFIG

Path to the directory with the HttpFS configuration files

${OZONE_CONF_DIR}

HTTPFS_LOG

Path to the directory with the HttpFS logs

${OZONE_LOG_DIR}

HTTPFS_TEMP

Path to the HttpFS temporary directory

${OZONE_LOG_DIR}

HADOOP_PID_DIR

Path to the directory where HttpFS stores process ID files

${OZONE_LOG_DIR}

HDFS_HTTPFS_OPTS

JVM options for the HttpFS service

-Xms700m -Xmx8G

httpfs.http.port

Port of the HttpFS service

14001

hadoop.http.temp.dir

Path to the temporary directory for the HttpFS service

${hadoop.tmp.dir}/httpfs

httpfs.hadoop.config.dir

Path to the Hadoop configuration directory for HttpFS

/etc/ozone/conf

httpfs.http.administrators

List of administrators for HttpFS service

*

httpfs.proxyuser.om.groups

List of user groups for Ozone Manager authentication in HttpFS

*

httpfs.proxyuser.om.hosts

List of hosts for Ozone Manager authentication in HttpFS

*

httpfs.proxyuser.hue.groups

List of user groups for HUE authentication in HttpFS

*

httpfs.proxyuser.hue.hosts

List of hosts for HUE authentication in HttpFS

*

httpfs.hadoop.authentication.kerberos.keytab

Kerberos keytab for Ozone Manager authentication in HttpFS

 — 

httpfs.hadoop.authentication.kerberos.principal

Kerberos principal for Ozone Manager authentication in HttpFS

 — 

httpfs.hadoop.authentication.type

Authentication mechanism for Ozone Manager

simple

hadoop.http.authentication.kerberos.keytab

Path to Kerberos keytab for HttpFS authentication

 — 

hadoop.http.authentication.kerberos.principal

Kerberos principal for HttpFS authentication

 — 

hadoop.http.authentication.type

Authentication mechanism for HttpFS

simple

httpfs.ssl.enabled

Defines whether SSL is enabled for HttpFS

false

Custom httpfs-env.sh

 — 

Custom httpfs-site.xml

 — 

Enable custom ulimits

Switch on the corresponding toggle button to specify resource limits (ulimits) for the current process. If you do not set these values, the default system settings are used. Ulimit settings are described in the table below

LimitCPU

A limit in seconds on the amount of CPU time that a process can consume

cpu time ( -t)

LimitFSIZE

Maximum size of files that a process can create, in 512-byte blocks

file size ( -f)

LimitDATA

Maximum size of a process’s data segment, in kilobytes

data seg size ( -d)

LimitSTACK

Maximum stack size allocated to a process, in kilobytes

stack size ( -s)

LimitCORE

Maximum size of a core dump file allowed for a process, in 512-byte blocks

core file size ( -c)

LimitRSS

The maximum amount of RAM memory (resident set size) that can be allocated to a process, in kilobytes

max memory size ( -m)

LimitNOFILE

Maximum number of open file descriptors allowed for the process

open files ( -n)

LimitAS

Maximum size of the process virtual memory (address space), in kilobytes

virtual memory ( -v)

LimitNPROC

Maximum number of processes

max user processes ( -u)

LimitMEMLOCK

Maximum memory size that can be locked for the process, in kilobytes. Memory locking ensures the memory is always in RAM and a swap file is not used

max locked memory ( -l)

LimitLOCKS

Maximum number of files locked by a process

file locks ( -x)

LimitSIGPENDING

Maximum number of signals that are pending for delivery to the calling thread

pending signals ( -i)

LimitMSGQUEUE

Maximum number of bytes in POSIX message queues. POSIX message queues allow processes to exchange data in the form of messages

POSIX message queues ( -q)

LimitNICE

Maximum NICE priority level that can be assigned to a process

scheduling priority ( -e)

LimitRTPRIO

Maximum real-time scheduling priority level

real-time priority ( -r)

LimitRTTIME

Maximum pipe buffer size, in 512-byte blocks

pipe size ( -p)

ozone.om.address

Address of the Ozone Manager

0.0.0.0:9862

ozone.om.enable.filesystem.paths

Defines whether the filesystem path-style operations are enabled

true

ozone.om.http-address

HTTP address of the Ozone Manager web interface

0.0.0.0:9874

ozone.om.https-address

HTTPS address of the Ozone Manager web interface

0.0.0.0:9875

ozone.om.ratis.port

Port for Ratis communication used by Ozone Manager

9858

ozone.om.db.dirs

Path to the directory where the Ozone Manager stores its database files

/srv/ozone/meta/db

ozone.om.db.dirs.permissions

750

ozone.metadata.dirs

Path to the directory for general metadata storage in Ozone

/srv/ozone/meta

ozone.metadata.dirs.permissions

750

ozone.om.snapshot.diff.db.dir

Path to the directory for storing the snapshot diff database for Ozone Manager

/srv/ozone/meta/snapshot

ozone.om.ratis.enable

Defines whether the Ratis-based replication for Ozone Manager is enabled to ensure high availability

true

ozone.om.service.ids

Identifiers for the Ozone Manager services used in multi-instance setups for high availability

 — 

ozone.om.kerberos.principal

Ozone Manager service principal

 — 

ozone.om.kerberos.keytab.file

Path to the keytab file used by the Ozone Manager daemon as its service principal to log in with

 — 

ozone.om.http.auth.type

Authentication mechanism for the Ozone Manager HTTP server

simple

ozone.om.http.auth.kerberos.principal

Principal of the Ozone Manager HTTP server service if SPNEGO is enabled

 — 

ozone.om.http.auth.kerberos.keytab

Path to the keytab file used by the Ozone Manager HTTP server as its service principal to log in with if SPNEGO is enabled

 — 

Custom ozone-site.conf

 — 

Enable custom ulimits

Switch on the corresponding toggle button to specify resource limits (ulimits) for the current process. If you do not set these values, the default system settings are used. Ulimit settings are described in the table below

LimitCPU

A limit in seconds on the amount of CPU time that a process can consume

cpu time ( -t)

LimitFSIZE

Maximum size of files that a process can create, in 512-byte blocks

file size ( -f)

LimitDATA

Maximum size of a process’s data segment, in kilobytes

data seg size ( -d)

LimitSTACK

Maximum stack size allocated to a process, in kilobytes

stack size ( -s)

LimitCORE

Maximum size of a core dump file allowed for a process, in 512-byte blocks

core file size ( -c)

LimitRSS

The maximum amount of RAM memory (resident set size) that can be allocated to a process, in kilobytes

max memory size ( -m)

LimitNOFILE

Maximum number of open file descriptors allowed for the process

open files ( -n)

LimitAS

Maximum size of the process virtual memory (address space), in kilobytes

virtual memory ( -v)

LimitNPROC

Maximum number of processes

max user processes ( -u)

LimitMEMLOCK

Maximum memory size that can be locked for the process, in kilobytes. Memory locking ensures the memory is always in RAM and a swap file is not used

max locked memory ( -l)

LimitLOCKS

Maximum number of files locked by a process

file locks ( -x)

LimitSIGPENDING

Maximum number of signals that are pending for delivery to the calling thread

pending signals ( -i)

LimitMSGQUEUE

Maximum number of bytes in POSIX message queues. POSIX message queues allow processes to exchange data in the form of messages

POSIX message queues ( -q)

LimitNICE

Maximum NICE priority level that can be assigned to a process

scheduling priority ( -e)

LimitRTPRIO

Maximum real-time scheduling priority level

real-time priority ( -r)

LimitRTTIME

Maximum pipe buffer size, in 512-byte blocks

pipe size ( -p)

ozone.recon.db.dir

Path to the directory where Recon stores its database files for metrics and reports

/srv/ozone/recon/db

ozone.recon.task.pipelinesync.interval

Interval for the pipeline sync task, which synchronizes the pipeline information from Storage Container Manager

120s

ozone.recon.task.missingcontainer.interval

Interval for the missing container check, used to identify and report missing containers in the cluster

3600s

ozone.recon.http-address

HTTP address for the Recon web interface, used to view metrics and reports for the Ozone cluster

0.0.0.0:9888

ozone.recon.https-address

HTTPS address for the Recon web interface

0.0.0.0:9889

ozone.recon.kerberos.principal

Recon service principal

 — 

ozone.recon.kerberos.keytab.file

Path to the keytab file used by the Recon daemon as its service principal to log in with

 — 

ozone.recon.http.auth.type

Authentication mechanism for the Recon HTTP server

simple

ozone.recon.http.auth.kerberos.principal

Principal of the Recon HTTP server service for Kerberos authentication

 — 

ozone.recon.http.auth.kerberos.keytab

Path to the keytab file used by the Recon HTTP server as its service principal to log in with

 — 

Custom ozone-site.conf

 — 

Enable custom ulimits

Switch on the corresponding toggle button to specify resource limits (ulimits) for the current process. If you do not set these values, the default system settings are used. Ulimit settings are described in the table below

LimitCPU

A limit in seconds on the amount of CPU time that a process can consume

cpu time ( -t)

LimitFSIZE

Maximum size of files that a process can create, in 512-byte blocks

file size ( -f)

LimitDATA

Maximum size of a process’s data segment, in kilobytes

data seg size ( -d)

LimitSTACK

Maximum stack size allocated to a process, in kilobytes

stack size ( -s)

LimitCORE

Maximum size of a core dump file allowed for a process, in 512-byte blocks

core file size ( -c)

LimitRSS

The maximum amount of RAM memory (resident set size) that can be allocated to a process, in kilobytes

max memory size ( -m)

LimitNOFILE

Maximum number of open file descriptors allowed for the process

open files ( -n)

LimitAS

Maximum size of the process virtual memory (address space), in kilobytes

virtual memory ( -v)

LimitNPROC

Maximum number of processes

max user processes ( -u)

LimitMEMLOCK

Maximum memory size that can be locked for the process, in kilobytes. Memory locking ensures the memory is always in RAM and a swap file is not used

max locked memory ( -l)

LimitLOCKS

Maximum number of files locked by a process

file locks ( -x)

LimitSIGPENDING

Maximum number of signals that are pending for delivery to the calling thread

pending signals ( -i)

LimitMSGQUEUE

Maximum number of bytes in POSIX message queues. POSIX message queues allow processes to exchange data in the form of messages

POSIX message queues ( -q)

LimitNICE

Maximum NICE priority level that can be assigned to a process

scheduling priority ( -e)

LimitRTPRIO

Maximum real-time scheduling priority level

real-time priority ( -r)

LimitRTTIME

Maximum pipe buffer size, in 512-byte blocks

pipe size ( -p)

ozone.s3g.http-address

HTTP address for the S3 Gateway, which provides the S3-compatible API for Ozone

0.0.0.0:9878

ozone.s3g.https-address

HTTPS address for the S3 Gateway

0.0.0.0:9879

ozone.s3g.volume.name

Specifies the volume name used by the S3 Gateway for storing S3-compatible buckets in Ozone

s3v

ozone.s3g.client.buffer.size

Size of the client buffer used by the S3 Gateway for data transfers

4KB

ozone.s3g.kerberos.principal

S3 Gateway service principal

 — 

ozone.s3g.kerberos.keytab.file

Path to the keytab file used by the S3 Gateway as its service principal to log in with

 — 

ozone.s3g.http.auth.type

Authentication mechanism for the S3G HTTP server

simple

ozone.s3g.http.auth.kerberos.principal

The S3 Gateway service principal if SPNEGO is enabled for the HTTP server

 — 

ozone.s3g.http.auth.kerberos.keytab

Path to the keytab file used by the S3 Gateway HTTP server as its service principal to log in with if SPNEGO is enabled

 — 

Custom ozone-site.conf

 — 

Enable custom ulimits

Switch on the corresponding toggle button to specify resource limits (ulimits) for the current process. If you do not set these values, the default system settings are used. Ulimit settings are described in the table below

LimitCPU

A limit in seconds on the amount of CPU time that a process can consume

cpu time ( -t)

LimitFSIZE

Maximum size of files that a process can create, in 512-byte blocks

file size ( -f)

LimitDATA

Maximum size of a process’s data segment, in kilobytes

data seg size ( -d)

LimitSTACK

Maximum stack size allocated to a process, in kilobytes

stack size ( -s)

LimitCORE

Maximum size of a core dump file allowed for a process, in 512-byte blocks

core file size ( -c)

LimitRSS

The maximum amount of RAM memory (resident set size) that can be allocated to a process, in kilobytes

max memory size ( -m)

LimitNOFILE

Maximum number of open file descriptors allowed for the process

open files ( -n)

LimitAS

Maximum size of the process virtual memory (address space), in kilobytes

virtual memory ( -v)

LimitNPROC

Maximum number of processes

max user processes ( -u)

LimitMEMLOCK

Maximum memory size that can be locked for the process, in kilobytes. Memory locking ensures the memory is always in RAM and a swap file is not used

max locked memory ( -l)

LimitLOCKS

Maximum number of files locked by a process

file locks ( -x)

LimitSIGPENDING

Maximum number of signals that are pending for delivery to the calling thread

pending signals ( -i)

LimitMSGQUEUE

Maximum number of bytes in POSIX message queues. POSIX message queues allow processes to exchange data in the form of messages

POSIX message queues ( -q)

LimitNICE

Maximum NICE priority level that can be assigned to a process

scheduling priority ( -e)

LimitRTPRIO

Maximum real-time scheduling priority level

real-time priority ( -r)

LimitRTTIME

Maximum pipe buffer size, in 512-byte blocks

pipe size ( -p)

ozone.scm.http-address

HTTP address for the Storage Container Manager web interface

0.0.0.0:9876

ozone.scm.https-address

HTTPS address for the Storage Container Manager web interface

0.0.0.0:9877

ozone.scm.ratis.port

Port for Ratis communication used by Storage Container Manager for high availability

9894

ozone.scm.db.dirs

Path to the directory where Storage Container Manager stores its database files

/srv/ozone/scm/db

ozone.scm.db.dirs.permissions

750

ozone.scm.ha.ratis.storage.dir

Path to the directory for storing Ratis logs for high availability in Storage Container Manager

/srv/ozone/scm/ratis

ozone.scm.ha.ratis.snapshot.dir

Path to the directory for storing Ratis snapshots in Storage Container Manager

/srv/ozone/scm/ratis/snapshot

ozone.scm.service.ids

Identifiers for Storage Container Manager services used in multi-instance setups for high availability

 — 

ozone.scm.primordial.node.id

Specifies the ID of the first Storage Container Manager node in the cluster

{{ groups['ozone.ozone_scm'][0] }}

ozone.scm.names

Comma-separated list of fully qualified domain names (FQDNs) for the Storage Container Manager nodes in the cluster

{{ groups['ozone.ozone_scm'] | join(',') }}

ozone.scm.client.address

Comma-separated list of addresses for the Storage Container Manager clients, typically FQDNs of Storage Container Manager nodes

{{ groups['ozone.ozone_scm'] | join(',') }}

ozone.scm.ratis.enable

Defines whether the Ratis-based replication is enabled for Storage Container Manager to ensure high availability

true

ozone.scm.datanode.pipeline.limit

Maximum number of pipelines each Datanode can be part of in Storage Container Manager

10

ozone.scm.pipeline.owner.container.count

Maximum number of containers owned by each pipeline

10

ozone.scm.pipeline.creation.auto.factor.one

Defines whether Storage Container Manager should automatically create pipelines with a replication factor of one

false

ozone.scm.container.placement.impl

Specifies the container placement policy for Storage Container Manager, typically to optimize disk usage based on available capacity

org.apache.hadoop.hdds.scm.container.placement.algorithms.SCMContainerPlacementCapacity

ozone.scm.kerberos.principal

Storage Container Manager service principal

 — 

ozone.scm.kerberos.keytab.file

Path to the keytab file used by the Storage Container Manager daemon as its service principal to log in with

 — 

ozone.scm.http.auth.type

Authentication mechanism for the Storage Container Manager HTTP server

simple

ozone.scm.http.auth.kerberos.principal

Principal of the Storage Container Manager service if SPNEGO is enabled for the HTTP server

 — 

ozone.scm.http.auth.kerberos.keytab

Path to the keytab file used by the Storage Container Manager HTTP server as its service principal to log in with if SPNEGO is enabled

 — 

Custom ozone-site.conf

 — 

Enable custom ulimits

Switch on the corresponding toggle button to specify resource limits (ulimits) for the current process. If you do not set these values, the default system settings are used. Ulimit settings are described in the table below

LimitCPU

A limit in seconds on the amount of CPU time that a process can consume

cpu time ( -t)

LimitFSIZE

Maximum size of files that a process can create, in 512-byte blocks

file size ( -f)

LimitDATA

Maximum size of a process’s data segment, in kilobytes

data seg size ( -d)

LimitSTACK

Maximum stack size allocated to a process, in kilobytes

stack size ( -s)

LimitCORE

Maximum size of a core dump file allowed for a process, in 512-byte blocks

core file size ( -c)

LimitRSS

The maximum amount of RAM memory (resident set size) that can be allocated to a process, in kilobytes

max memory size ( -m)

LimitNOFILE

Maximum number of open file descriptors allowed for the process

open files ( -n)

LimitAS

Maximum size of the process virtual memory (address space), in kilobytes

virtual memory ( -v)

LimitNPROC

Maximum number of processes

max user processes ( -u)

LimitMEMLOCK

Maximum memory size that can be locked for the process, in kilobytes. Memory locking ensures the memory is always in RAM and a swap file is not used

max locked memory ( -l)

LimitLOCKS

Maximum number of files locked by a process

file locks ( -x)

LimitSIGPENDING

Maximum number of signals that are pending for delivery to the calling thread

pending signals ( -i)

LimitMSGQUEUE

Maximum number of bytes in POSIX message queues. POSIX message queues allow processes to exchange data in the form of messages

POSIX message queues ( -q)

LimitNICE

Maximum NICE priority level that can be assigned to a process

scheduling priority ( -e)

LimitRTPRIO

Maximum real-time scheduling priority level

real-time priority ( -r)

LimitRTTIME

Maximum pipe buffer size, in 512-byte blocks

pipe size ( -p)