Bug 1041529 - [RFE][swift]: Support chanaging the ring size
Summary: [RFE][swift]: Support chanaging the ring size
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/swif...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 16:50 UTC by RHOS Integration
Modified: 2015-03-19 16:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:56:35 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 16:50:15 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/ring-doubling.

Description:

This work follows in the steps of previous efforts to allow changes to the ring size during the life of a cluster.
I.e. to allow growing the number of partitions of the swift ring which is set to be 2^part_power.
Such a change can allow a cluster to start small and grow as needed, as it removes the requirement to define number of partitions in advance during initial cluster installation.

The basic idea behind such efforts is that one can double every entry in the ring without changing the placement 
(i.e. such that the same keys will continue to be mapped to the same a/c/o servers). 

As well explained in https://bugs.launchpad.net/swift/+bug/933803, doubling the ring introduces an additional challenge at the a/c/o servers. The a/c/o servers are using the partition number as part of the path in which they store objects. Naively increasing the number of partitions therefore will keep the mapping between the swift devices (server disks) constant but will require restructuring the the directory tree at each device. 

This work seek to resolve that challenge and design a solution that will not require restructuring the the directory tree at each device.



Specification URL (additional information):

None


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