Changes in one node cause the dropping of the same entry in another node's cache
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
-
It has been observed that when a user makes an update of the cache in one node, it removes that entry from the cache in other nodes.
Resolution
- This is an expected behavior.
-
When an entity change is persisted, Liferay broadcasts a message to all nodes via JGroups. The message is akin to: "web content id 36745689 is updated".
- Upon receiving the message, the node will expire that entry, if it is in the cache. A subsequent retrieve of the updated entity will be a “cache miss” and will be retrieved from the database and added to the cache again, this makes it current.
Did this article resolve your issue ?
