Actions
Story #9079
closed
Investigate additional mitigations to cache invalidation issues
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello, Performance
Sprint:
Quarter:
Description
Ticket moved to GitHub: "pulp/pulpcore/2026":https://github.com/pulp/pulpcore/issues/2026
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.
Additionally there could be smaller transient errors that prevent invalidation events from going through.
The time window this damage can manifest is pretty small (10 minutes as of #8996) but we should investigate further methods of mitigation. One example could be - pulpcore detecting when the Redis connection has failed, and either retrying cache invalidations, or flushing the cache entirely.
Related issues
Updated by dalley almost 3 years ago
- Copied from Issue #8996: Mitigate cache invalidation issues with a reduced default expiration time. added
Updated by dalley almost 3 years ago
- Tracker changed from Issue to Task
- % Done set to 0
- Severity deleted (
2. Medium) - Triaged deleted (
No)
Updated by dalley almost 3 years ago
- Tracker changed from Task to Issue
- Severity set to 2. Medium
- Triaged set to No
Setting it back to an issue so it can go through triage.
Updated by dkliban@redhat.com over 2 years ago
- Tracker changed from Issue to Story
- % Done set to 0
- Severity deleted (
2. Medium) - Triaged deleted (
No)
Updated by pulpbot over 2 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions
.