[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. |
| 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. |