Joining nodes ignore clustered cache in JBEDS - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)