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

[DOC] Feature in 2.2 requires two variables documented. #850

Closed
2 of 4 tasks
nateynateynate opened this issue Aug 4, 2022 · 1 comment
Closed
2 of 4 tasks

[DOC] Feature in 2.2 requires two variables documented. #850

nateynateynate opened this issue Aug 4, 2022 · 1 comment

Comments

@nateynateynate
Copy link
Member

nateynateynate commented Aug 4, 2022

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request.

When 2.2 comes out, the feature regarding shard allocation awareness (#3367) relies on two configuration variables being set. These variables are not very well described, with their only mention being at https://opensearch.org/docs/2.0/opensearch/cluster/#advanced-step-6-configure-shard-allocation-awareness-or-forced-awareness

Do you have any related resources to help us get started?

For example, a link to a related fixed issue, a design doc, or any particular POCs (Eng or PM) who have more information?

opensearch-project/OpenSearch#3367
https://opensearch.org/docs/2.0/opensearch/cluster/#advanced-step-6-configure-shard-allocation-awareness-or-forced-awareness

cluster.routing.allocation.awareness.attributes and cluster.routing.allocation.awareness.force.zone.values

Is there anything else you'd like to add?

They are documented... elsewhere..... just not on our site.

@Naarcha-AWS
Copy link
Collaborator

@nateynateynate: We already have an issue for Awareness Attributes in progress, see PR https://github.com/opensearch-project/documentation-website/pull/856/files and issue #828.

Going to close this one, feel free to comment on the linked PR if you want any additional information added to the doc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants