Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1205869 - [RFE][swift] Swift ring overload concept
[RFE][swift] Swift ring overload concept
Status: CLOSED UPSTREAM
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-swift (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity medium
: z5
: 7.0 (Kilo)
Assigned To: Pete Zaitcev
Mike Abrams
https://blueprints.launchpad.net/swif...
: FutureFeature, Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-25 15:58 EDT by Sean Cohen
Modified: 2017-08-31 11:57 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Imbalance in tiers in Swift was previously addressed by weights. However, no matter what the numerical ratio of weight is set, at a certain point there are not enough devices and replicas remaining in lower weight tiers to balance out the crowding at the higher weight tier. At this moment, the tier becomes underutilized, while an administrator may need to force more than one replica into tier to achieve utilization. The ratio of more-than-1 partition is the overload parameter. This update permits administrators to store more than one replica in a tier in case of severely unbalanced clusters. As a result, it is now possible so sacrifice data durability in order to achieve better utilization, which in some cases is required for availability. For example, a cluster will fail to store new data if low-weight tiers overflow and quorum fails.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-31 11:57:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Comment 8 Mike McCune 2016-03-28 19:46:50 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Note You need to log in before you can comment on or make changes to this bug.