Joining nodes ignore clustered cache in JBEDS
Issue
- Using an internal materialized view in JBEDS 5.1 with CP2, a node which re-joins the cluster is ignoring the cache available in the cluster causing out-of-sync caches.
- This behavior happens when the restarting 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)
Environment
- JBoss Enterprise Data Service Platform (JBEDS) 5.1
- Start 2 nodes in a cluster with a vdb deployed which has an internal materialized view (IMV).
- Query the IMV on node 1 to populate the cache on node 1.
- Query the IMV on node 2 to populate the cache on node 2 from node 1.
- 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
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
