[MGNLADVCACHE-10] Make cache cluster aware Created: 23/Apr/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Advanced Cache
Component/s: None
Affects Version/s: 1.1
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently when Magnolia is deployed in clustered environment, cache content is kept separate for each cluster node as it is stored outside of JCR. This however means that cache updates, or more precisely forcing pages to be removed from the cache explicitly (because for some reason we know they were updated, like when adding page comment) will not work properly as such event will not be propagated to instance of the cache running on other cluster node.
The existing implementation will still work fine for general use case when we need to flush cache upon activation which is observation based and therefore propagated for cluster nodes.
For more other use cases, like commenting, we should provide an API that will do the same (propagate the flush request using observation) for flushing individual content.



 Comments   
Comment by Jan Haderka [ 24/Apr/09 ]

Created concept page for further discussion about usefulness and possible solutions for the feature http://wiki.magnolia-cms.com/display/DEV/Concept+Caching+In+Clustered+Env

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Sun Feb 11 23:10:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.