I think Redbo makes a good point about a single drive failure making the system unable to return success being unfortunate. I wasn't really thinking about it that way. I'm starting to lean towards "certain enough".
For example, if we only return 500 when one of the nodes is specifically returning 419, and allow 202's if we get a timeout or 507 from just one node - the one in a gazillion chance that replication leads to a resurrected container almost assuredly trends toward one in a Googolplex. -- 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
