Node Configuration Properties

Node configuration properties are applied individually to each node in a cluster. The following describes each node configuration property, with its default setting if applicable.

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

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

To learn how to set these properties from studying a sample configuration file, see the node configuration sample.

Required properties

You must include the following required properties in your configuration. If you omit them, Redpanda will not start.


Path to the directory for storing Redpanda’s streaming data files.

Optional properties


IP address and port of the admin server.



Path to the admin API documentation directory.

Default: /usr/share/redpanda/admin-api-doc


TLS configuration for the Admin API.

Default: null


Addresses of Kafka API published to clients.

Default: empty array


Address of the RPC endpoint published to other cluster members.

Default: null


The directory where the cache archive is stored. This property is mandatory when cloud_storage_enabled is set to true.

Default: null


IP address and port for supervisor service.



A limit on the number of consecutive times a broker can crash within one hour before its crash-tracking logic is reset. This limit prevents a broker from getting stuck in an infinite cycle of crashes.

If null, the property is disabled and no limit is applied.

The crash-tracking logic is reset (to zero consecutive crashes) by any of the following conditions:

  • The node shuts down cleanly.

  • One hour elapses since the last crash.

  • The node configuration file, redpanda.yaml, is updated.

  • The startup_log file in the node’s data_directory is manually deleted.

Units: number of consecutive crashes of a node

Default: null


Path to the directory where the HTTP dashboard is located.

Default: null


Enabling developer_mode isn’t recommended for production use.

Flag to enable developer mode, which skips most of the checks performed at startup.

Default: false


Controls how a new cluster is formed. This property must have the same value in all nodes in a cluster.

If true, an empty seed_servers list will denote that this node should form a cluster. At most, one node in the cluster should be configured with an empty seed_servers list. If no such configured node exists, or if configured to be false, all nodes denoted by the seed_servers list must be identical among those nodes' configurations, and those nodes will form the initial cluster.

While it’s set true by default for backward compatibility, Redpanda recommends that you set empty_seed_starts_cluster to false.

Default: true


IP address and port of the Kafka API endpoint that handles requests.



Transport Layer Security (TLS) configuration for the Kafka API endpoint.

Default: null


Enables log warning messages for memory allocations greater than the given threshold size, in bytes.

If set to null, the property is disabled, so no log messages are enabled.

If enabled, the log warnings are rate limited: the first warning will be for any allocation greater than or equal to the configured threshold, then for every subsequent warning the threshold is increased by 1.618x the current threshold.

Units: bytes per memory allocation

Default: null


A number that uniquely identifies the node within the cluster. If null (the default value), Redpanda automatically assigns an ID. If set, it must be non-negative value.

The node_id property mustn’t be changed after a node joins the cluster.

Default: null

Range: [0, …​]


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


IP address and port for the Remote Procedure Call (RPC) server.



TLS configuration for the RPC server.

Default: null


List of seed servers used to join an existing cluster.

If a cluster does not already exist:

  • 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.

  • Otherwise, 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