[
https://issues.redhat.com/browse/TEIID-5998?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-5998.
-----------------------------------
Resolution: Done
With the default of 20 active plans the max size of a temporary lob is 1/80 of the storage
space. With the default of 50 gb that is approximately 625 mb. A single large temporary
lob or set of lobs (for example from using copylobs) could easily exceed that. Once we
added TEIID-5584, we do a better job of recovering from out of disk situations (the
biggest possible downside is that in high concurrency situations more sessions than
necessary may be killed). So with this change we strike a different balance that will
allow for a larger max size. With the default of 20 active plans we'll now allow a
max size of 1/6 th of the storage space - anything larger than that is certainly
indicative of a problem that should be killed immediately. The actual calculation is max
space / max active plans ^ .6 so that even much higher numbers of active plans can still
have rather large lobs.
Relax the maxFileStoreLength based upon TEIID-5584
--------------------------------------------------
Key: TEIID-5998
URL:
https://issues.redhat.com/browse/TEIID-5998
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 15.0
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Based upon
https://github.com/teiid/teiid/issues/1314 we should relax the individual max
file length to allow for session killing to be utilized if needed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)