GET/HEAD should stop continuing to search more nodes if a tombstone is reached
Bug #1560574 reported by
Caleb Tennis
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Medium
|
Thiago da Silva |
Bug Description
If we encounter a tombstone, we should just return a 404 vs. continuing to search more nodes for actual object data.
Changed in swift: | |
assignee: | nobody → rohita joshi (rjoshi16) |
Changed in swift: | |
assignee: | rohita joshi (rjoshi16) → nobody |
Changed in swift: | |
assignee: | nobody → Thiago da Silva (thiagodasilva) |
Changed in swift: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
I'm not so sure this is a good idea. It may end up just pushing the problem around.
Right now, we have a case where a PUT to 3 nodes, then a DELETE to 2 nodes, then a GET might return a 200. However, we have another case where a PUT to 3 nodes, then a DELETE to 3 nodes, then a PUT to 2 nodes, then a GET will always return a 200.
I think that, if we make the requested behavior change in Swift, we'll have another bug report in six months complaining of a 404 after a PUT(3)/ DELETE( 3)/PUT( 2)/GET sequence.
I could be wrong though.