[
https://issues.jboss.org/browse/TEIID-4758?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4758:
-------------------------------------
Even in server mode, when the data source itself goes down, there is no notification.
Teiid only tracks the addition/removal of data source connection configuration not the
data source itself. When a data source goes, WF can't give a valid connection, but VDB
is still considers active as the connection configuration is complete. We would need to
come up with another way the proactively validate the "liveliness" sources for
this.
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
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)