[
https://issues.jboss.org/browse/TEIID-4758?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-4758:
------------------------------------
As you indicated, when the source goes down, the VDB may still be in active state. And
assuming no VDB is being deployed, what would trigger the rescheduling?
Permanent materialization load failure is when target source goes
down
----------------------------------------------------------------------
Key: TEIID-4758
URL:
https://issues.jboss.org/browse/TEIID-4758
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.12
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 9.3
During the external materialization load, if the target cache database goes offline, the
materialization job stops, but the {{Status}} table is left in {{LOADING}} state, which
will never recover when the target cache database comes back up again.
This situation is observed when JDG is used in OpenShift along with JDV However, behavior
can occur in standalone situations too. The system should resilient and must recover in
this situation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)