Issue #8996
closed
Mitigate cache invalidation issues with a reduced default expiration time.
Status:
CLOSED - CURRENTRELEASE
Tags:
Katello, Performance
Description
If Redis goes down, Pulp can no longer invalidate / clear out the cache appropriately while it is offline, and when it comes back up it will be out of date.
We should mitigate this by reducing the default expiration time while investigating more comprehensive solutions.
- Priority changed from Normal to High
- Category set to Installer - Moved to GitHub issues
- Severity changed from 2. Medium to 3. High
- Sprint set to Sprint 100
- Description updated (diff)
- Subject changed from Disable Redis persistence to [EPIC] Cache invalidation issues
- Category deleted (
Installer - Moved to GitHub issues)
- Priority changed from High to Normal
- Severity changed from 3. High to 2. Medium
- Sprint deleted (
Sprint 100)
- Tags Performance added
- Tags deleted (
Easy Fix)
- Subject changed from [EPIC] Cache invalidation issues to Mitigate cache invalidation issues with a reduced default expiration time.
- Description updated (diff)
- Status changed from NEW to POST
- Sprint/Milestone set to 3.14.2
- Copied to Backport #9063: Backport 8996 "Reduce cache entry expiration TTL" to 3.14.z added
- Triaged changed from No to Yes
- Sprint set to Sprint 100
- Sprint/Milestone deleted (
3.14.2)
- Sprint/Milestone set to 3.14.2
- Sprint/Milestone changed from 3.14.2 to 3.15.0
- Copied to Story #9079: Investigate additional mitigations to cache invalidation issues added
- Status changed from POST to MODIFIED
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Reduce the cache entry expiration TTL
If Redis goes down then its persisted data can get out of sync with Pulp, because cache invalidation events cannot occur. We should mitigate the impact by letting cache entries expire after a shorter period of time.
closes: #8996 https://pulp.plan.io/issues/8996