Skip to main content
Version: 22.3

Node Configuration Properties

Node configuration properties are applied individually to each node in a cluster. The following table lists each node configuration property in alphabetical order, along with its description and default setting.

After you change a node-level property setting, you must restart the node for the change to take effect.

Required properties

PropertyDescription
data_directoryThe folder where Redpanda streaming data files are stored.

Default: /var/lib/redpanda/data

Optional properties

PropertyDescription
adminAddress and port of the admin server.

Default: 127.0.0.1:9644
admin_api_doc_dirPath to the admin API documentation directory.

Default: /usr/share/redpanda/admin-api-doc
admin_api_tlsTLS configuration for the Admin API.

Default: Null
advertised_kafka_apiAddress of Kafka API published to clients.

Default: an empty array
advertised_rpc_apiAddress of the RPC endpoint published to other cluster members.

Default: Null
cloud_storage_cache_directoryThe directory where the cache archive is stored. This property is mandatory when cloud_storage_enabled is set to true.

Default: Null
coproc_supervisor_serverIP address and port for supervisor service.

Default: 127.0.0.1:43189
dashboard_dirThe directory where the HTTP dashboard is located.

Default: Null
developer_modeSkips most of the checks performed at startup. Not recommended for production use.

Default: True
empty_seed_starts_clusterControls how a new cluster is formed. This property must have the same value in all nodes in a cluster.

Recommended: False
Default: True, for backward compatibility
kafka_apiAddress of the Kafka API that handles requests.

Default: 127.0.0.1:9092
kafka_api_tlsTransport Layer Security (TLS) configuration for the Kafka API endpoint.

Default: Null
node_idA number that uniquely identifies the node within the cluster. This property must not be changed after a node joins the cluster.

If unset, Redpanda assigns one automatically. If set, it must be a positive number.

Default: Null
rackA rack is a label that identifies a failure zone. Apply the same label to all nodes in the same failure zone. When enable_rack_awareness is set to true at the cluster level, the system uses the rack labels to spread partition replicas across different failure zones.

Default: Null
rpc_serverRemote Procedure Call (RPC) server IP address.

Default: 127.0.0.1:33145
rpc_server_tlsTLS configuration for RPC server.

Default: Null
seed_serversList of seed servers used to join an existing cluster. If a cluster does not already exist, then:

When empty_seed_starts_cluster is true, if the seed_servers list is empty, this node will be the cluster root to form a new cluster that other nodes subsequently join. Exactly one node in the cluster should set seed_servers to be empty when first bootstrapping a cluster. For nodes that are not the root node, this is the list of nodes used to join the cluster.

When empty_seed_starts_cluster is false, this refers to the list of nodes that initially bootstrap the cluster. In this case, seed_servers cannot be empty, and seed_servers must be identical for all nodes in that list. For nodes not in the seed_servers list, this is the list of nodes used to join the cluster.

Default: Null