-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
async-search is_partial=true when any shard search fails or times out #98913
async-search is_partial=true when any shard search fails or times out #98913
Conversation
Hi @quux00, I've created a changelog YAML for you. |
Pinging @elastic/es-search (Team:Search) |
41e3327
to
f236c2e
Compare
When merged, be sure to inform the Kibana team, as they have a related change they need to make: elastic/kibana#164893 |
With the recent addition of per-cluster metadata to the `_clusters` section of the response for cross-cluster searches (see elastic#97731), the `is_partial` setting in the async-search response, now acts as a useful summary to end-users that search/aggs data from all shards is potentially incomplete (not all shards fully searched), which could be for one of 3 reasons: 1. at least one shard was not successfully searched (a PARTIAL search cluster state) 2. at least one cluster (marked as `skip_unavailable`=`true`) was unavailable (or all searches on all shards of that cluster failed), causing the cluster to be marked as SKIPPED 3. a search on at least one cluster timed out (`timed_out`=`true`, resulting in a PARTIAL cluster search status) This commit changes local-only (non-CCS) searches to behave consistently with cross-cluster searches, namely, if any search on any shard fails or if the search times out, the is_partial flag is set to true. Closes elastic#98725
f236c2e
to
4793600
Compare
Hey team, thanks for looking into this! The elastic/kibana#164893 issue is our team's (@elastic/kibana-data-discovery), and I just wanted to ask if we could get a heads up with a couple of days notice if you decide to merge this if possible? We have an idea of how we might handle it on the Kibana side, but we've been holding off implementing anything until we're sure this is going to be merged. |
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.
LGTM!
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
With the recent addition of per-cluster metadata to the
_clusters
section of the response for cross-cluster searches (see #97731), theis_partial
setting in the async-search response, now acts as a useful summary to end-users that search/aggs data from all shards is potentially incomplete (not all shards fully searched), which could be for one of 3 reasons:skip_unavailable
=true
) was unavailable (or all searches on all shards of that cluster failed), causing the cluster to be marked as SKIPPEDtimed_out
=true
, resulting in a PARTIAL cluster search status)This commit changes local-only (non-CCS) searches to behave consistently with cross-cluster searches, namely, if any search on any shard fails or if the search times out, the is_partial flag is set to true.
Closes #98725
Relates #55572