[MGNLCACHE-166] Flush cache when new light-module resources are pushed to the server Created: 28/Feb/17  Updated: 15/Jul/22  Resolved: 11/Dec/17

Status: Closed
Project: Cache Modules
Component/s: cache core
Affects Version/s: None
Fix Version/s: 5.6.1

Type: Bug Priority: Critical
Reporter: Ervin Vystup Assignee: Roman Kovařík
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLCACHE-190 Backport: Flush cache when new light-... Closed
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Sprint: Kromeriz 119, Kromeriz 123
Story Points: 5

 Description   

During pushing resources to an app server would be good to flush a cache memory to reflect made changes after updating in Magnolia.



 Comments   
Comment by Jan Haderka [ 23/Oct/17 ]

It is questionable, and part of solving this issue, to decide whether we flush "on file system origin changes" or when there are any changes in registries.
While first would be as close to origin as possible, latter might be more "systematic" and aligning architecture by allowing us to stop observation for JCR configuration and also reflect changes to registries caused by registering anything directly by code.
Also what is the effect of cache on web resources served by light modules? Are those cached at all? If yes, what is the benefit of such caching and wouldn't serving them from filesystem actually improve performance of whole server?

Please re-estimate in light of those questions and time necessary to find answers to them. Removing original estimate.

Comment by Roman Kovařík [ 08/Nov/17 ]

esienczylo

Do I understand correctly that with this fix , any change in the light modules will flush the cache?

See above.

And why it won't be provided with 5.6?

Just a timing issue, the feature had been implemented when the feature development for 5.6 was already closed.

Comment by Viet Nguyen [ 16/Nov/17 ]

Anyone please update our fixed version, rkovarik, ahietala?

Comment by Roman Kovařík [ 28/Nov/17 ]

Reopened: to be ported to 5.5.x.

Comment by Roman Kovařík [ 11/Dec/17 ]

Closing again, separate ticket for the backport created (MGNLCACHE-190).

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