-
Quality Risk
-
Resolution: Done
-
Major
-
None
-
None
Even with tweaks to the behavior of setting hard limits for a single buffer and all session memory consumption - they are not a great way of dealing with over consumption of resources. Heap memory usage is already pretty well subdivided based upon reserve limits, the max processing setting, max active plans, etc. It would be best to simply react to the out of disk event by victimizing the session consuming the most resources.
- is related to
-
TEIID-5525 add a flag to revert to the prior behavior (TEIID-4557)
- Resolved