Re: [Openstack] [Swift] Container DB update after object PUT

2013-12-03 Thread Pete Zaitcev
On Thu, 28 Nov 2013 05:24:35 + "Shao, Minglong" wrote: > 1. Proxy server sends three requests to three object servers. > 2. One object server writes the object successfully, sends an update to > the container DB and an “OK” reply to the proxy server. But the other two > fail, so they

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-30 Thread Shao, Minglong
Thanks for the clarification! Best, -Minglong On 11/29/13, 4:26 PM, "Samuel Merritt" mailto:s...@swiftstack.com>> wrote: On 11/27/13 9:24 PM, Shao, Minglong wrote: Thanks for your reply! I understand the three PUTs by the proxy server and how the replicator works. What I don’t understand is th

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-29 Thread Samuel Merritt
On 11/27/13 9:24 PM, Shao, Minglong wrote: Thanks for your reply! I understand the three PUTs by the proxy server and how the replicator works. What I don’t understand is the update of the container DB. The update is sent by individual object servers which don’t know whether a PUT (from the clie

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-29 Thread Kuo Hugo
gt; To: Minglong Shao > Cc: "openstack@lists.openstack.org" > Subject: Re: [Openstack] [Swift] Container DB update after object PUT > > Proxy will interrupt the PUT request to the only good device. > > Object server returned error to Proxy > https://github.com/openstac

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-28 Thread Shao, Minglong
mailto:tonyt...@gmail.com>> Date: Thursday, November 28, 2013 at 5:46 PM To: Minglong Shao mailto:minglong.s...@netapp.com>> Cc: "openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>" mailto:openstack@lists.openstack.org>> Subject: Re: [Openstack]

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-28 Thread Kuo Hugo
cause it >doesn’t meet the quorum. But the container DB still gets the update to >insert an entry of this object. > > I must have missed something. Thanks for your help! > > From: Kuo Hugo > Date: Thursday, November 28, 2013 at 12:31 PM > To: Minglong Shao > Cc: &quo

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-27 Thread Shao, Minglong
:31 PM To: Minglong Shao mailto:minglong.s...@netapp.com>> Cc: "openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>" mailto:openstack@lists.openstack.org>> Subject: Re: [Openstack] [Swift] Container DB update after object PUT Proxy sends requests to

Re: [Openstack] [Swift] Container DB update after object PUT

2013-11-27 Thread Kuo Hugo
Proxy sends requests to *three* replicas's object servers simultaneously. A successful PUT request depends on at least 1/2 replicas were success. Or Proxy will return PUT failed to user. If 1/3 replica is not there, the replicator will handle it later. It won't have any problem with container DB.

[Openstack] [Swift] Container DB update after object PUT

2013-11-27 Thread Shao, Minglong
Hi there, After an object server writes an object in the local file system, it updates the container DB asynchronously (send a message to insert an entry in the object table). But the object server doesn’t really know whether the object PUT is considered successful or not because the other two