Skip to content

Commit c52d6ed

Browse files
committed
DOC-4939 Copied changes from PR #1103 to 7.4 version of optimize shards placement REST API reference
1 parent e4f05c9 commit c52d6ed

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/operate/rs/7.4/references/rest-api/requests/bdbs/actions/optimize_shards_placement.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Get optimized shards placement for the given database.
3636
#### Example HTTP request
3737

3838
```sh
39-
GET /bdbs/1/actions/optimize_shards_placement
39+
GET /v1/bdbs/1/actions/optimize_shards_placement
4040
```
4141

4242
#### Query parameters
@@ -55,12 +55,12 @@ Include query parameters in a `GET` request to generate an optimized shard place
5555
The following example request includes `shards_count` and `memory_size` as query parameters:
5656

5757
```sh
58-
GET /bdbs/1/actions/optimize_shards_placement?shards_count=10&memory_size=10000
58+
GET /v1/bdbs/1/actions/optimize_shards_placement?shards_count=10&memory_size=10000
5959
```
6060

6161
### Response {#get-response}
6262

63-
To rearrange the database shards, you can submit the blueprint returned in this response body as the `shards_blueprint` field in the [`PUT` `/bdbs/{uid}`](#put-bdbs-rearrange-shards) request.
63+
To rearrange the database shards, you can submit the blueprint returned in this response body as the `shards_blueprint` field in the [`PUT` `/v1/bdbs/{uid}`](#put-bdbs-rearrange-shards) request.
6464

6565
#### Example JSON body
6666

@@ -125,9 +125,9 @@ To rearrange the database shards, you can submit the blueprint returned in this
125125

126126
## Rearrange database shards {#put-bdbs-rearrange-shards}
127127

128-
Use the blueprint returned by the [`GET`&nbsp;`/bdbs/{uid}/actions/optimize_shards_placement`]({{< relref "/operate/rs/references/rest-api/requests/bdbs/actions/optimize_shards_placement#get-bdbs-actions-optimize-shards-placement" >}}) request as the value of the `shards_blueprint` field to rearrange the database shards.
128+
Use the blueprint returned by the [`GET`&nbsp;`/v1/bdbs/{uid}/actions/optimize_shards_placement`]({{< relref "/operate/rs/references/rest-api/requests/bdbs/actions/optimize_shards_placement#get-bdbs-actions-optimize-shards-placement" >}}) request as the value of the `shards_blueprint` field to rearrange the database shards.
129129

130-
To ensure that the optimized shard placement is relevant for the current cluster state, pass the `cluster-state-id`, taken from the response header of the `GET` request, in the [`PUT`&nbsp;`/bdbs/{uid}`]({{< relref "/operate/rs/references/rest-api/requests/bdbs#put-bdbs" >}}) request headers.
130+
To ensure that the optimized shard placement is relevant for the current cluster state, pass the `cluster-state-id`, taken from the response header of the `GET` request, in the [`PUT`&nbsp;`/v1/bdbs/{uid}`]({{< relref "/operate/rs/references/rest-api/requests/bdbs#put-bdbs" >}}) request headers.
131131

132132
The cluster will reject the update if its state was changed since the optimal shards placement was obtained.
133133

@@ -136,7 +136,7 @@ The cluster will reject the update if its state was changed since the optimal sh
136136
#### Example HTTP request
137137

138138
```sh
139-
PUT /bdbs/1
139+
PUT /v1/bdbs/1
140140
```
141141

142142
#### Headers

0 commit comments

Comments
 (0)