Changes in one node cause the dropping of the same entry in another node's cache

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.

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.