[
https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5525:
-------------------------------------
I'm not sure what you are saying here. Reducing the batch size
will not help the overall amount of committed memory.
I was entirely thinking it was
heap issue, that if processing batch size is reduced then it may take more time but will
not run into issues with overflow going to disk. But it looks like what you found is
overestimation on the size of the disk which is inadvertently erroring out.
add a flag to revert to the prior behavior (TEIID-4557)
-------------------------------------------------------
Key: TEIID-5525
URL:
https://issues.jboss.org/browse/TEIID-5525
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.12.14.6_4, 8.12.15.6_4
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.0, 11.2.1
Several customers are seeing errors[1] after
https://issues.jboss.org/browse/TEIID-4557
was implemented and generally have to drop the max-active-plans to 1 for their queries to
succeed. Can a flag be added to revert to the behavior prior to TEIID-4557?
[1]
ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0:
org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a
single operation/table id 85 has been exceeded. The server may need to increase the
amount of disk or memory available, or decrease the number of max active plans.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)