Object remains on handoff after DELETE

[Chuck Thier]

When a user issues a DELETE, and an object is on a handoff node, the handoff object does not get deleted. This normally wouldn't be a big issues, except a HEAD or GET on the object will still find it, thus not appearing to be deleted by the user, at least until replication gets to the object. I'm not advocating that we issue a DELETE to all handoff nodes as well, but should figure out some way to handle this case.

It could be argued to chalk it up to eventual consistency, but I think it warrants trying to handle in a reasonable way.

[John Dickinson (notmyname)]

I wonder if we can differentiate at the proxy server an object server saying "404 I didn't find it" and "404 I found a tombstone with timestamp X". Then the proxy can do the right thing (ie probably keep looking into handoffs and only return if a newer non-404 isn't returned).

[Chuck Thier (cthier)]

Yeah that was one possibility that we were discussing here as well

[Samuel Merritt (torgomatic)]

Pretty sure the object server 404 response has an X-Timestamp if there was a tombstone, and no X-Timestamp if there wasn't.

[Thiago da Silva (thiagodasilva)]

I think this bug is a duplicate of bug #1560574. The behavior is explained in a different way, but I believe the solution will turn to be the same.