Skip to content

Commit

Permalink
Removes max_primary_shard_size parameter (#1914)
Browse files Browse the repository at this point in the history
* Removes max_primary_shard_size parameter

Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>

* Added a comment on the new parameter

Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>

Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
(cherry picked from commit cb9b5a6)
  • Loading branch information
kolchfa-aws authored and github-actions[bot] committed Nov 28, 2022
1 parent 27b2a86 commit f4a124d
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions _api-reference/index-apis/shrink-index.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,4 +58,8 @@ You can use the request body to configure some index settings for the target ind
Field | Type | Description
alias | Object | Sets an alias for the target index. Can have the fields `filter`, `index_routing`, `is_hidden`, `is_write_index`, `routing`, and `search_routing`. See [Index Aliases]({{site.url}}{{site.baseurl}}/api-reference/alias/#request-body).
settings | Object | Index settings you can apply to your target index. See [Index Settings]({{site.url}}{{site.baseurl}}/api-reference/index-apis/create-index/#index-settings).

{% comment %}
The new parameter to be called max_shard_size.
max_primary_shard_size | Bytes | Sets the maximum size of a primary shard in the target index. For example, if this field is set to 100 GB, and the source index's primary shards total to 300 GB, then the target index has 3 primary shards of 100 GB each.
{% endcomment %}

0 comments on commit f4a124d

Please sign in to comment.