[
https://issues.jboss.org/browse/TEIID-1782?page=com.atlassian.jira.plugin...
]
Paul Nittel commented on TEIID-1782:
------------------------------------
After seeing the TTL wasn't in the transformation, I fixed that and retried my
querying. The auto-refresh worked correctly.
Then I examined each node individually. One node was updated, but the other was not.
Depending on the node to which the user connected, they would see different results.
That's the point of this bug report.
Internal materialized views are not refreshed on both nodes in a
Single, Non-Multihomed, Server
-----------------------------------------------------------------------------------------------
Key: TEIID-1782
URL:
https://issues.jboss.org/browse/TEIID-1782
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4.1
Environment: Fedora 14
Reporter: Paul Nittel
Assignee: Steven Hawkins
Priority: Blocker
Attachments: PartsSourceA-ds.xml, PartsSourceB-ds.xml, SimpleMatView.vdb
I have a cluster which is configured as a two-node single, non-multihomed, server. On
each node (deployed as "Production" and named "node1" and
"node2") I have deployed identical datasources and VDB.
Shouldn't Materialized View management take place on all nodes in a cluster?
The servers are started using:
nohup ./run.sh -c node1 -g EDSPartition -b IPaddress -u 239.255.100.100
-Djboss.Domain=EDS -Djboss.jvmRoute="node1" -Djboss.messaging.ServerPeerID=1
-Djboss.service.binding.set=ports-default &>node1.out &
nohup ./run.sh -c node2 -g EDSPartition -b IPaddress -u 239.255.100.100
-Djboss.Domain=EDS -Djboss.jvmRoute="node2" -Djboss.messaging.ServerPeerID=2
-Djboss.service.binding.set=ports-01 &>node2.out &
I connect to the VDB using the following URL:
mm://IPaddress:31000,IPaddress:31100
Querying the IMV table (PartsVirtual.SupplierInfo) loads one of the nodes, but not both.
I can refresh both nodes by CALLing SYSADMIN.refreshMatView on each node in the cluster.
Additionally, the transformation being queried contains a TTL of 30 seconds which never
appears to expire. (It works as expected in a non-clustered environment.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira