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.
Path to the admin API documentation directory.
The directory where the cache archive is stored. This property is mandatory when cloud_storage_enabled is set to
Flag to enable developer mode, which skips most of the checks performed at startup.
Controls how a new cluster is formed. This property must have the same value in all nodes in a cluster.
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
IP address and port of the Kafka API endpoint that handles requests.
Transport Layer Security (TLS) configuration for the Kafka API endpoint.
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.
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.
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.