Bug 1205869
| Summary: | [RFE][swift] Swift ring overload concept | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Sean Cohen <scohen> |
| Component: | openstack-swift | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED UPSTREAM | QA Contact: | Mike Abrams <mabrams> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | derekh, mabrams, panbalag, scohen, sgotliv, srevivo, thiago, zaitcev |
| Target Milestone: | z5 | Keywords: | FutureFeature, Triaged, ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/swift/+spec/ring-overload | ||
| Whiteboard: | |||
| 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 15:57:36 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
2015-03-25 19:58:37 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions |