[
https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4661:
---------------------------------------
With internal materialization, there is no ttl-driven load running in
background, is there?
If materialization management is enabled, then yes there will be - in this case you
don't have that enabled.
So it is safe to wait longer than ttl for it to expire and expect
that next load is triggered only when the view is queried, isn't it?
With lazy-invalidate there isn't a hard guarantee on the timing. On a heavily loaded
box it may not complete when expected.
Is my testing approach incorrect?
The primary concerns here are that the materialization is getting refreshed and that
subsequent queries aren't hanging. If we are transitioning back out of the loading
state and this is just a timing issue, then it's not a concern.
Subsequent queries hang after materialized view TTL expires.
------------------------------------------------------------
Key: TEIID-4661
URL:
https://issues.jboss.org/browse/TEIID-4661
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.12.x
Reporter: Colin Mondesir
Assignee: Steven Hawkins
Priority: Critical
Fix For: 9.0.6, 9.1.2, 9.2, 8.12.10.6_3
With a VDB using lazy-invalidate in a clustered configuration initially the materialized
view is cached correctly but when the TTL expires (10 minutes) and the query is run again
the state of the view changes to LOADING and never reverts to "LOADED", so the
next query hangs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)