Actions
Backport #22575
closedjewel: Random 500 errors in Swift PutObject
Release:
jewel
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Updated by Nathan Cutler over 6 years ago
- Copied from Bug #22517: Cache never becoming consistent after failed updates added
Updated by Nathan Cutler over 6 years ago
- Status changed from New to Need More Info
The changes seem too extensive for jewel. Is the jewel backport really necessary?
Updated by Matt Benjamin over 6 years ago
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
Updated by Matt Benjamin over 6 years ago
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)?
Updated by Adam Emerson over 6 years ago
Here's Matt's jewel backport. I beefed up the description on the original bug.
Updated by Nathan Cutler over 6 years ago
- Description updated (diff)
- Status changed from Need More Info to In Progress
- Assignee set to Matt Benjamin
Updated by Nathan Cutler about 6 years ago
- Status changed from In Progress to Resolved
- Target version set to v10.2.11
Actions