Bug 1316594

Summary: [RFE][swift] Put part-replicas where they go
Product: Red Hat OpenStack Reporter: Sean Cohen <scohen>
Component: openstack-swiftAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: derekh, jjoyce, mabrams, mlopes, srevivo, zaitcev
Target Milestone: gaKeywords: FutureFeature
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-swift-2.7.0-2.el7ost Doc Type: Enhancement
Doc Text:
This enhancement adds improved replica placement, and protection from duplicated assignments. This was added because, in the traditional Swift layout, the act of accidentally assigning two replicas of a partition to the same device resulted in a silent reduction of durability. As a result, duplicate assignments are prevented, thereby adhering to calculated guarantees. However, since this requires the number of devices to be no less than the number of replicas, it is possible for certain incorrect old rings to be considered invalid. Consequently, it is still possible to have the number of zones be smaller than the number of replicas.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-11 12:14:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sean Cohen 2016-03-10 14:48:39 UTC
Deal with unduplicate device part replica assignment in Swift

See also validate against duplicate device part replica assignment https://review.openstack.org/#/c/222799/

Comment 2 Mike McCune 2016-03-28 23:47:57 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 9 errata-xmlrpc 2016-08-11 12:14:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1597.html