Project

Profile

Help

Story #9079

Investigate additional mitigations to cache invalidation issues

Added by dalley 3 months ago. Updated 3 months ago.

Status:
NEW
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

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

Copied from Pulp - Issue #8996: Mitigate cache invalidation issues with a reduced default expiration time.CLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by dalley 3 months ago

  • Copied from Issue #8996: Mitigate cache invalidation issues with a reduced default expiration time. added

#2 Updated by dalley 3 months ago

  • Tracker changed from Issue to Task
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

#3 Updated by dalley 3 months 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.

#4 Updated by dkliban@redhat.com 3 months ago

  • Tracker changed from Issue to Story
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

Please register to edit this issue

Also available in: Atom PDF