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.
You must include the following required properties in your configuration. If you omit them, Redpanda will not start.
|data_directory||The folder where Redpanda streaming data files are stored.|
|admin||Address and port of the admin server. |
|admin_api_doc_dir||Path to the admin API documentation directory. |
|admin_api_tls||TLS configuration for the Admin API. |
|advertised_kafka_api||Address of Kafka API published to clients. |
Default: an empty array
|advertised_rpc_api||Address of the RPC endpoint published to other cluster members. |
|cloud_storage_cache_directory||The directory where the cache archive is stored. This property is mandatory when cloud_storage_enabled is set to true. |
|coproc_supervisor_server||IP address and port for supervisor service. |
|dashboard_dir||The directory where the HTTP dashboard is located. |
|developer_mode||Skips most of the checks performed at startup. Not recommended for production use. |
|empty_seed_starts_cluster||Controls how a new cluster is formed. This property must have the same value in all nodes in a cluster.|
Default: True, for backward compatibility
|kafka_api||Address of the Kafka API that handles requests. |
|kafka_api_tls||Transport Layer Security (TLS) configuration for the Kafka API endpoint. |
|node_id||A 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.|
|rack||A 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. |
|rpc_server||Remote Procedure Call (RPC) server IP address. |
|rpc_server_tls||TLS configuration for RPC server. |
|seed_servers||List 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.