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
In a Cross Cluster Search (CCS) environment, it's possible for different clusters to serve different data tiers in responses.
If one of the requested clusters responds slowly with data from the frozen tier, this can cause a timeout at the proxy after 320s, and 502 responses presented as failure toast messages in the UI with no data loaded.
Solution? Don't allow APM to query the frozen tier.
Description
In a Cross Cluster Search (CCS) environment, it's possible for different clusters to serve different data tiers in responses.
If one of the requested clusters responds slowly with data from the frozen tier, this can cause a timeout at the proxy after 320s, and 502 responses presented as failure toast messages in the UI with no data loaded.
Solution? Don't allow APM to query the frozen tier.
Resources
Which documentation set does this change impact?
Stateful and Serverless
Feature differences
@crespocarlos to clarify
What release is this request related to?
8.16
Collaboration model
The documentation team
Point of contact.
Main contact: @crespocarlos
The text was updated successfully, but these errors were encountered: