[
https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin...
]
Pedro Inácio commented on TEIID-4734:
-------------------------------------
Hi,
I've observed that there is another situation where the views are no longer updated.
I don't know if you want me to open this in a different Ticket or not.
The situation is the following:
For some unknown reason, sometimes a materialized view takes more time to finish the
load/update than the one defined in transaction timeout (300 seconds is the default
value).
The transaction reaper will kill the update transaction. The _LoadState_ in _status_ table
will be *LOADING*.
Any subsequent try to update the view will fail, since the system reads the state as being
*LOADING* even if the system is not currently updating it.
Example log next.
The update took too long (more than 10 minutes [defined transaction timeout]):
{code:batch}
2017-02-17 16:10:44,487 INFO [org.teiid.COMMAND_LOG] (NIO6) gZueFR0aNjgi START USER
COMMAND: startTime=2017-02-17 16:10:44.487 requestID=gZueFR0aNjgi.11
txID=null sessionID=gZueFR0aNjgi applicationName=JDBC principal=manel
vdbName=CountryServiceListVDB vdbVersion=1 sql={call SYSADMIN.loadMatView(?, ?)}
2017-02-17 16:20:44,528 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117:
TransactionReaper::check timeout for TX 0:ffff0a080174:21ddbdf0:58a71a32:cb in state RUN
2017-02-17 16:20:44,564 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0)
ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker
0,5,main] successfully canceled TX 0:ffff0a080174:21ddbdf0:58a71a32:cb
{code}
Next I tried to update the view:
{code:batch}
2017-02-17 16:29:21,272 INFO [org.teiid.COMMAND_LOG] (NIO2) E1xyKpChGKvC START USER
COMMAND: startTime=2017-02-17 16:29:21.272 requestID=E1xyKpChGKvC.7
txID=null sessionID=E1xyKpChGKvC applicationName=JDBC principal=manel
vdbName=CountryServiceListVDB vdbVersion=1 sql=EXECUTE
SYSADMIN.loadMatView('CountryServiceListCalculatedRaw','country_service_list_calculated_raw')
2017-02-17 16:29:21,391 INFO [org.teiid.COMMAND_LOG] (Worker25_QueryProcessorQueue18136)
E1xyKpChGKvC END USER COMMAND: endTime=2017-02-17 16:29:21.391
requestID=E1xyKpChGKvC.7 txID=null sessionID=E1xyKpChGKvC principal=manel
vdbName=CountryServiceListVDB vdbVersion=1 finalRowCount=1
{code}
And nothing happened.
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.3
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)