Actions
Bug #51674
closedPotential race condition in robust notify
% Done:
0%
Source:
Tags:
Backport:
pacific,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Notifications can fail. This we know.
When they do, rather than repeating the update, which can lead to A-B-A style races, we should blow the object out of peer cache.
Updated by Adam Emerson almost 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51678: octopus: Potential race condition in robust notify added
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51679: pacific: Potential race condition in robust notify added
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51680: nautilus: Potential race condition in robust notify added
Updated by Adam Emerson over 2 years ago
- Status changed from Pending Backport to Resolved
- Backport changed from pacific,octopus,nautilus to pacific,octopus
Updated by Casey Bodley 9 months ago
- Related to Bug #62250: retry metadata cache notifications with INVALIDATE_OBJ added
Actions