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
When running with cortex query frontend module with query spliting enabled, in case the query request in a long-range (e.g. 30-day) query, the final response query frontend received could be very large, say 3,4GBs, and it could potentially result instance OOM killed.
So I'm wondering if there is a way to prevent a bunch of requests or single big request consuming more than limit size? Does cortex has any functionality to safeguard the instance from OOM kill scenarios?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Community,
When running with cortex query frontend module with query spliting enabled, in case the query request in a long-range (e.g. 30-day) query, the final response query frontend received could be very large, say 3,4GBs, and it could potentially result instance OOM killed.
So I'm wondering if there is a way to prevent a bunch of requests or single big request consuming more than limit size? Does cortex has any functionality to safeguard the instance from OOM kill scenarios?
Beta Was this translation helpful? Give feedback.
All reactions