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.

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

[BUG] max_primary_shard_size parameter does not exist in Shrink API #5170

Closed
gaobinlong opened this issue Nov 9, 2022 · 1 comment
Closed
Labels
bug Something isn't working distributed framework

Comments

@gaobinlong
Copy link
Collaborator

gaobinlong commented Nov 9, 2022

Describe the bug
As the Shrink API's document says, there is a request parameter named max_primary_shard_size which can be used to set the maximum size of a primary shard in the target index, but the parameter does not exist in opensearch actually.

To Reproduce

POST a/_shrink/e
{
  "max_primary_shard_size":"50gb"
}

the response is :

{
  "error" : {
    "root_cause" : [
      {
        "type" : "x_content_parse_exception",
        "reason" : "[2:3] [resize_request] unknown field [max_primary_shard_size]"
      }
    ],
    "type" : "x_content_parse_exception",
    "reason" : "[2:3] [resize_request] unknown field [max_primary_shard_size]"
  },
  "status" : 400
}

Expected behavior
Maybe we should remove the request parameter max_primary_shard_size from the document temporarily and add it back after we implement the function.

Screenshots
image

Host/Environment (please complete the following information):

  • OS: [MacOS]
  • Version [12.6]
  • OpenSearch Version: 2.3
@gaobinlong
Copy link
Collaborator Author

Close this issue as the related PR has been merged yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working distributed framework
Projects
None yet
Development

No branches or pull requests

3 participants