Backport #22575
closed
- Copied from Bug #22517: Cache never becoming consistent after failed updates added
- Status changed from New to Need More Info
The changes seem too extensive for jewel. Is the jewel backport really necessary?
basically, in my judgment, yes. these fixes arise from experience with multi-gateway setups in the field. note that there were additional changes originally in this series that just optimized cached lookups--those have been removed
looking at this ticket now, would it help if we beefed up the description and maybe reproducer hints? @adamemerson, could you take a pass at that (being careful to sanitize downstream data)?
- Description updated (diff)
- Status changed from Need More Info to In Progress
- Assignee set to Matt Benjamin
- Status changed from In Progress to Resolved
- Target version set to v10.2.11
Also available in: Atom
PDF