Bug #51674
closed
Potential race condition in robust notify
Added by Adam Emerson almost 3 years ago.
Updated over 2 years ago.
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.
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #51678: octopus: Potential race condition in robust notify added
- Copied to Backport #51679: pacific: Potential race condition in robust notify added
- Copied to Backport #51680: nautilus: Potential race condition in robust notify added
- Status changed from Pending Backport to Resolved
- Backport changed from pacific,octopus,nautilus to pacific,octopus
- Related to Bug #62250: retry metadata cache notifications with INVALIDATE_OBJ added
Also available in: Atom
PDF