rpk redpanda mode
This command is not supported on macOS, Windows. |
Development mode
Development mode (development
or dev
) includes the following development-only settings:
-
Sets
developer_mode
totrue
. This starts Redpanda with dev-mode only settings, including:-
No minimal memory limits are enforced.
-
No core assignment rules for Redpanda nodes are enforced.
-
Enables write caching, which is a relaxed mode of
acks=all
that acknowledges a message as soon as it is received and acknowledged on a majority of brokers, without waiting for it to fsync to disk. This provides lower latency while still ensuring that a majority of brokers acknowledge the write. For more information, or to disable this, see write caching. -
Bypasses
fsync
(from Seastar optionunsafe_bypass_fsync
), which results in unrealistically fast clusters and may result in data loss.
-
-
Sets
overprovisioned
totrue
. Redpanda expects a dev system to be an overprovisioned environment. Based on a Seastar option, settingoverprovisioned
disables thread affinity, zeros idle polling time, and disables busy-poll for disk I/O. -
Sets all autotuner tuners to
false
. The tuners are intended to run only for production mode.
Production mode
Production mode (production
or prod
) disables dev-mode settings:
-
developer_mode: false
-
overprovisioned: false
It also enables a set of tuners of the autotuner. For descriptions about the tuners, see Tuners in the rpk redpanda tune list command reference.
Recovery mode
Recovery mode (recovery
) sets the broker configuration property recovery_mode_enabled
to true
. This provides a stable environment for troubleshooting and restoring a failed cluster.
Flags
Value | Type | Description |
---|---|---|
|
- |
Help for mode. |
|
string |
Redpanda or |
|
stringArray |
Override rpk configuration settings; |
|
string |
Profile to use. See |
|
- |
Enable verbose logging. |