Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update note re Maint mode #876

Merged
merged 1 commit into from
Dec 2, 2024
Merged

Update note re Maint mode #876

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions modules/manage/pages/node-management.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ When a broker is placed in maintenance mode, if the replication factor is greate
====
* Maintenance mode only transfers leadership. It does not move any partitions to other brokers in the cluster.
* If a broker hosts a partition with a replica count of one, the partition is unavailable when the Redpanda process is not running.
* Maintenance mode operations only handle a single broker in maintenance at a time. If you attempt to place more than one broker in maintenance mode, you will get an error.
====

The amount of time it takes to drain a broker and reassign leadership depends on the number of partitions and the health of the cluster. For healthy clusters, draining leadership should take less than a minute. For unhealthy clusters (for example, when follower is not in sync with the leader), draining the broker can take longer. Note that the draining process won't start until the cluster is healthy.
Expand Down
Loading