Skip to content

Document that awareness attributes override custom preferences #83818

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

Merged
merged 4 commits into from
Feb 11, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,14 @@ GET /my-index-000001/_search?preference=my-custom-shard-string
----
// TEST[setup:my_index]

WARNING: If a node has <<shard-allocation-awareness,shard allocation awareness>>
attributes, then it will prefer shards with the same awareness attribute values.
Because of these attributes, different coordinating nodes may route the same
search differently, even if the searches use the same custom `preference`
values. To disable routing based on awareness attributes, set the
`es.search.ignore_awareness_attributes` system property to `true` in the
<<set-jvm-options,JVM options>> of every node in the cluster.

NOTE: If the cluster state or selected shards change, the same `preference`
string may not route searches to the same shards in the same order. This can
occur for a number of reasons, including shard relocations and shard failures. A
Expand Down