-
Bug
-
Resolution: Unresolved
-
Critical
-
ACM 2.12.0, ACM 2.13.2
-
None
-
Incidents & Support
-
False
-
-
False
-
-
-
Search Sprint 2025-18
-
Important
-
Customer Reported
-
None
Description of problem:
The query sent by the Argo integration is consuming too much memory & cpu causing PostgreSQL to crashLoopback because of OOM
Version-Release number of selected component (if applicable): 2.13.2
How reproducible:
Observed on customer environment with Argo applications.
Steps to Reproduce:
- TBD
- ...
Actual results:
High cpu + memory utilization by the recursive query to resolve Argo app relationships.
Expected results:
Query resolves with lower cpu + memory resources.
Additional info:
- clones
-
ACM-22418 Search query from Argo integration causing postgres to OOM
-
- Review
-