-
Notifications
You must be signed in to change notification settings - Fork 44
Rolling restart Admin API #1026
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,6 +7,13 @@ This topic includes new content added in version {page-component-version} Beta. | |
* xref:redpanda-cloud:get-started:whats-new-cloud.adoc[] | ||
* xref:redpanda-cloud:get-started:cloud-overview.adoc#redpanda-cloud-vs-self-managed-feature-compatibility[Redpanda Cloud vs Self-Managed feature compatibility] | ||
|
||
== New health probes for broker restarts and upgrades | ||
|
||
The Redpanda Admin API now includes new health probes to help you ensure safe broker restarts and upgrades. The xref:api:ROOT:admin-api.adoc#get-/v1/broker/pre_restart_probe[`pre_restart_probe`] endpoint identifies potential risks if a broker is restarted, and xref:api:ROOT:admin-api.adoc#get-/v1/broker/post_restart_probe[`post_restart_probe`] indicates how much of its workloads a broker has reclaimed after the restart. See also: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @kbatuigas please check these links. Is the API just not updated yet? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. never mind: I see https://github.com/redpanda-data/docs/pull/1019/files |
||
|
||
* xref:manage:cluster-maintenance/rolling-restart.adoc[] | ||
* xref:upgrade:rolling-upgrade.adoc[] | ||
|
||
== Redpanda Console v3.0.0 (beta) | ||
|
||
The Redpanda Console v3.0.0 beta release includes the following updates: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,4 +11,19 @@ To view additional information about your brokers, run: | |
|
||
```bash | ||
rpk redpanda admin brokers list | ||
``` | ||
``` | ||
|
||
You can also use the xref:api:ROOT:admin-api.adoc#get-/v1/broker/post_restart_probe[Admin API] to check how much each broker has progressed in recovering its workloads: | ||
|
||
```bash | ||
curl -X GET "http://<broker-address>:<admin-api-port>/v1/broker/post_restart_probe" | ||
kbatuigas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
``` | ||
|
||
.Example output: | ||
[,json,role=no-copy] | ||
---- | ||
// Returns the load already reclaimed by broker, as a percentage of in-sync replicas | ||
{ | ||
"load_reclaimed_pc": 66 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is really nice @bashtanov ! Seems this will help a lot in building a smoother automated restart/upgrade automation @chrisseto @mmaslankaprv |
||
} | ||
---- |
Uh oh!
There was an error while loading. Please reload this page.