Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007CZ9L Steps to Reproduce: To recreate: 1. Start 2 nodes in a cluster with a vdb deployed which has an internal materialized view (IMV). 2. Query the IMV on node 1 to populate the cache on node 1. 3. Query the IMV on node 2 to populate the cache on node 2 from node 1. 4. Restart node 1 and query the IMV on node 1: Expectation: node 1 pulls cache from node 2 Actual: node 1 re-queries the source Note: this behavior happens when the restarting in step 4 is done gracefully (and node 2 is notified node 1 is leaving the cluster) as well as when it's done with an kill -9 (simulating a failure) project_key: SOA Using an internal materialized view in EDS 5.1 with CP2, a node which re-joins the cluster is ignoring the cache available in the cluster causing out-of-sync caches.
Link: Added: This issue depends TEIID-1592
Link: Added: This issue is duplicated by SOA-3119
Link: Removed: This issue depends TEIID-1592
This was addressed by TEIID-1493
Link: Removed: This issue is duplicated by SOA-3119
Link: Added: This issue depends TEIID-1493
TEIID-1493 is already part of 7.4. It was back ported to 7.1.1.CP3.
Release Notes Docs Status: Added: Not Yet Documented Writer: Added: dlesage
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3118 If an internal materialized view in was being used in EDS, a node which re-joined the cluster ignored the cluster's cache. This caused synchronisation issues. A patch has resolved this issue. As a result, nodes that rejoin the cluster now know to interrogate the cache.
Tested and closed.