[
https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5525:
---------------------------------------
However that should only be off by a factor of 2-3 (mostly due to
string estimation).
Actually object overhead in general adds a factor of 2. Using the engine tests show that
the heap memory estimate averages out to be 5 times higher than disk size. With the
performance tests it's an average of 8 times higher. So that is likely the root of
the issue - in scenarios that spill to disk, using an entirely heap based estimate of
memory usage overstates memory usage more than I had anticipated.
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)