Update container sync to use internal client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
https:/
commit 61a9d35fd58381b
Author: Yuan Zhou <email address hidden>
Date: Wed Dec 24 11:52:34 2014 +0800
Update container sync to use internal client
This patch changes container sync to use Internal Client instead
of Direct Client.
In the current design, container sync uses direct_get_object to
get the newest source object(which talks to storage node directly).
This works fine for replication storage policies however in
erasure coding policies, direct_get_object would only return part
of the object(it's encoded as several pieces). Using Internal
Client can get the original object in EC case.
Note that for the container sync put/delete part, it's working in
EC since it's using Simple Client.
Signed-off-by: Yuan Zhou <email address hidden>
DocImpact
Change-Id: I91952bc9337f35
Changed in openstack-manuals: | |
milestone: | none → liberty |
From my reading, this doesn't have user impact. If you think I'm wrong, please reopen with more information. Thanks, Lana.