Bug 1316594 - [RFE][swift] Put part-replicas where they go
Summary: [RFE][swift] Put part-replicas where they go
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-swift
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Pete Zaitcev
QA Contact: Mike Abrams
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 14:48 UTC by Sean Cohen
Modified: 2016-08-11 12:14 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2016-08-11 12:14:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 241571 0 None None None 2016-03-10 14:48:39 UTC
Red Hat Product Errata RHEA-2016:1597 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 9 Release Candidate Advisory 2016-08-11 16:06:52 UTC

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
Note You need to log in before you can comment on or make changes to this bug.