[
https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin...
]
Ramesh Reddy edited comment on TEIID-4734 at 2/11/17 11:09 AM:
---------------------------------------------------------------
[~shawkins] I updated the pull with much more cohesive solution using the JGroups which
works with Server and Embedded version, can take look and give any comments?
In this solution, I have used a JGroups Forked channel to establish registered nodes,
where this service notifies its listeners about node additions and drops.
On the materialization side, a new column "nodename" is added to the {{Status}}
table, which tracks which node is loading the materialization view. In the case when a
node goes down during the materialization load i.e. status stable is set to
"LOADING", then the above node tracker service notifies the
MaterializationService, which will reset the {{Status}} table to
"NEEDS_LOADING", and also kicks off another job to load the orphaned
materialized view load process.
In a single node scenario, upon restart the Materialization Service just checks the Status
table for any incomplete jobs and reset the Status table and schedules a new load of the
view .
was (Author: rareddy):
[~shawkins] I updated the pull with much more cohesive solution using the JGroups which
works with Server and Embedded version, can take look and give any comments?
Under some circumstances after restart Teiid Server does not update
Materialized views anymore
----------------------------------------------------------------------------------------------
Key: TEIID-4734
URL:
https://issues.jboss.org/browse/TEIID-4734
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 9.1.2
Environment: * Wildfly 10
* MySQL 5.6.32
* Teiid Server 9.1.2
Reporter: Pedro InĂ¡cio
Assignee: Ramesh Reddy
Fix For: 9.2
Attachments: StatusTableAfterStart.csv, StatusTableAfterStop.csv
Under some circumstances, start and stop the server several times at different points,
some Materialized Views are not being updated by the server.
It is observable that in status table some views are no longer updated. In server log are
being printed lots of INFO lines.
Waited more than 15 minutes and the server was not capable of recovering.
See the _StatusTableAfterStop.csv_ file to observe the status table content after
stopping the server.
See the _StatusTableAfterStart.csv_ file to observe the status table content after
approximately 15 minutes after restart.
Check _server.log_ for the Teiid Server log.
See that hundreds of lines similar to the following occur
{panel:title=Server.log}
2017-01-31 13:06:34,597 INFO [org.teiid.COMMAND_LOG] (Teiid Timer0) JfGY9cInAbrb START
USER COMMAND: startTime=2017-01-31
13:06:34.597 requestID=JfGY9cInAbrb.0 txID=null sessionID=JfGY9cInAbrb applicationName=internal principal=embedded-async vdbName=CountryServiceListVDB vdbVersion=1 sql=execute
SYSADMIN.matViewStatus('NumberingPlan', 'numbering_plan')
{panel}
The server cannot continue to load materialized views.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)