-
Notifications
You must be signed in to change notification settings - Fork 520
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
Add markers for cluster APIs. #9110
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Archer <naarcha@amazon.com>
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
Signed-off-by: Archer <naarcha@amazon.com>
Signed-off-by: Archer <naarcha@amazon.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Signed-off-by: Archer <naarcha@amazon.com>
Signed-off-by: Archer <naarcha@amazon.com>
Sent two fixes for cluster parameter descriptions:
These must be merged before this PR can move forward. |
Signed-off-by: Archer <naarcha@amazon.com>
Signed-off-by: Archer <naarcha@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some changes to be made in the documentation and in the spec. Thank you.
| Parameter | Data type | Description | Default | | ||
| :--- | :--- | :--- | :--- | | ||
| `include_disk_info` | Boolean | When `true`, returns information about disk usage and shard sizes. | `false` | | ||
| `include_yes_decisions` | Boolean | When `true`, returns any `YES` decisions in the allocation explanation. | `false` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we clarify this description? What's meant by YES
decisions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can do. Will open a adjustment PR in the opensearch-api-specification for this one.
index | String | The name of the shard's index. | ||
primary | Boolean | Whether to provide an explanation for the primary shard (true) or its first replica (false), which share the same shard ID. | ||
shard | Integer | The shard ID that you want an explanation for. | ||
`current_node` | String | If you only want an explanation if the shard happens to be on a particular node, specify that node name here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`current_node` | String | If you only want an explanation if the shard happens to be on a particular node, specify that node name here. | |
`current_node` | String | Specifies a node name to return an explanation only if the shard is on that node. |
shard | Integer | The shard ID that you want an explanation for. | ||
`current_node` | String | If you only want an explanation if the shard happens to be on a particular node, specify that node name here. | ||
`index` | String | The name of the shard's index. | ||
`primary` | Boolean | Whether to provide an explanation for the primary shard (true) or its first replica (false), which share the same shard ID. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`primary` | Boolean | Whether to provide an explanation for the primary shard (true) or its first replica (false), which share the same shard ID. | |
`primary` | Boolean | Whether to provide an explanation for the primary shard (`true`) or its first replica (`false`), both of which share the same shard ID. |
| :--- | :--- | :--- | | ||
| `node_ids` | List or String | A comma-separated list of node IDs to exclude from the voting configuration. When using this setting, you cannot also specify `node_names`. | | ||
| `node_names` | List or String | A comma-separated list of node names to exclude from the voting configuration. When using this setting, you cannot also specify `node_ids`. | | ||
| `timeout` | String | When adding a voting configuration exclusion, the API waits for the specified nodes to be excluded from the voting configuration before returning a response. If the timeout expires before the appropriate condition is satisfied, the request fails and returns an error. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default is 30 seconds. Please update the spec.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kolchfa-aws: How are you getting these defaults? Is there somewhere else in the code besides the spec where defaults are set?
| `node_ids` | List or String | A comma-separated list of node IDs to exclude from the voting configuration. When using this setting, you cannot also specify `node_names`. | | ||
| `node_names` | List or String | A comma-separated list of node names to exclude from the voting configuration. When using this setting, you cannot also specify `node_ids`. | | ||
| `timeout` | String | When adding a voting configuration exclusion, the API waits for the specified nodes to be excluded from the voting configuration before returning a response. If the timeout expires before the appropriate condition is satisfied, the request fails and returns an error. | | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this API support wait_for_removal
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not.
## Example request | ||
|
||
```json | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add an endpoint
"zone-3": 1 | ||
} | ||
} | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a copy button
@Naarcha-AWS would it be possible to have the validation capture this? This almost feels like a checklist is needed... the diffs show the "the default value is ..." translated to "N/A" . |
Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Part of issue #9050
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.