Yeah, the argument against (probably my) code comment was that resurrected containers are okay. IIRC it can only happen when the "no!" node had an object in it still that the other nodes didn't yet know about. If we allow the 204 in such a case, the user will think their container was deleted only to see it reappear with the offending object once things get in sync. In the vast majority of cases where the 3rd node says no, everything will end up meaning yes.
I put this bug in because Mike always pesters me about it, so you might grab his opinion. Generally speaking, we should 503 when we're not certain of the outcome. But at some point, we have to consider things certain enough. I'm fine with this one being on either side of that line. -- You received this bug notification because you are a member of Registry Administrators, which is subscribed to OpenStack Object Storage (swift). https://bugs.launchpad.net/bugs/665164 Title: Container DELETEs should only need a node majority to succeed _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : registry@lists.launchpad.net Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
