[
https://issues.jboss.org/browse/TEIID-5584?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5584.
-----------------------------------
Resolution: Done
Added the changes along with tests for the clob and table scenarios. However we cannot
yet guarantee that the current operation even with the termination of other sessions will
succeed as to prevent deadlocks we can't fully stop the world when killing and retry.
If that is a common occurrence, then the user can utilize the single operation or session
based memory limits.
Add/change resource limitation to be reactive to out of disk
------------------------------------------------------------
Key: TEIID-5584
URL:
https://issues.jboss.org/browse/TEIID-5584
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.0
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)