You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some digging, it seems that the sort for inner_hits is adding a considerable amount of time to the query.
The fix is to add the unmapped_type property to the sort clause which then immediately speeds up the query.
Because of this, our thinking is that because the metricbeat-* indices do not currently have the sort field in it's mappings (timestamp), Elasticsearch isn't handling something properly here. What is going on? I don't really know and I'm following up with @jimczi
The text was updated successfully, but these errors were encountered:
It's slow as a result of starting to search across
.monitoring-*
andmetricbeat-*
indices.After some digging, it seems that the
sort
forinner_hits
is adding a considerable amount of time to the query.The fix is to add the
unmapped_type
property to thesort
clause which then immediately speeds up the query.Because of this, our thinking is that because the
metricbeat-*
indices do not currently have thesort
field in it's mappings (timestamp
), Elasticsearch isn't handling something properly here. What is going on? I don't really know and I'm following up with @jimcziThe text was updated successfully, but these errors were encountered: