Bug 1257300

Summary: [RFE][swift] Increasing ring partition power
Product: Red Hat OpenStack Reporter: Sean Cohen <scohen>
Component: openstack-swiftAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: acanan, achernet, cschwede, derekh, egafford, jschluet, mabrams, nlevinki, pgrist, sclewis, scohen, sgotliv, srevivo, tvignaud, zaitcev
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://specs.openstack.org/openstack/swift-specs/specs/in_progress/increasing_partition_power.html
Whiteboard:
Fixed In Version: openstack-swift-2.14.1-0.20170707093649.4cb76a4.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1471629 (view as bug list) Environment:
Last Closed: 2017-12-13 20:33:46 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:
Bug Depends On:    
Bug Blocks: 1442136, 1471629    

Description Sean Cohen 2015-08-26 17:46:36 UTC
Problem Description

The ring power determines the partition to which a resource (account, container or object) is mapped. The partition is included in the path under which the resource is stored in a backend filesystem. Changing the partition power therefore requires relocating resources to new paths in backend filesystems.

In a heavily populated cluster a relocation process could be time-consuming and so to avoid down-time it is desirable to relocate resources while the cluster is still operating. However, it is necessary to do so without (temporary) loss of access to data and without compromising the performance of processes such as replication and auditing.

http://specs.openstack.org/openstack/swift-specs/specs/in_progress/increasing_partition_power.html

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

Comment 5 Elise Gafford 2016-10-05 11:22:54 UTC
Moving to 11 for triage and prio per discussion with the Swift squad. Resetting acks for reassessment.

Comment 21 errata-xmlrpc 2017-12-13 20:33:46 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://access.redhat.com/errata/RHEA-2017:3462