[
https://issues.jboss.org/browse/TEIID-4758?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4758:
-------------------------------------
Contrary to the comment as mentioned in the description of JIRA, when the databases do
comeback online the previous materialization job is not resumed but a new job will be
rescheduled to execute. So, the system does recover in my testing. If this not working for
JDG, then it may be isolated issue with that source.
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)