[MGNLADVCACHE-25] The ServeUntilRecachedPolicy and EagerRecachePolicy use a single global timestamp for all caches. Created: 02/Jul/14 Updated: 12/Nov/14 Resolved: 12/Nov/14 |
|
| Status: | Closed |
| Project: | Advanced Cache |
| Component/s: | None |
| Affects Version/s: | 1.4, 1.5 |
| Fix Version/s: | 1.6 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Rico Jansen | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cache, caching, vpro | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Both the ServeUntilRecachedPolicy and EagerRecachePolicy use a timestamp to determine if objects should be refreshed. However the flushpolicies There is only one timestamp there, so the timestamp is global for all caches configured with that policy so this does not work in multisite configurations or on single site with multiple cache configurations. |
| Comments |
| Comment by Roman Kovařík [ 12/Nov/14 ] |
|
ServeUntilRecachedCachePolicy still uses only one timestamp. |