openstack/swift
Code Issues Proposed changes

Update ring overview for reuse of device ids

Browse Source 
Change-Id: Ied15706d4cc931b5314001a02457f83e175c5d24
This commit is contained in:
Paul Dardeau 2016-03-17 22:12:42 +00:00
parent 902cb8f8d7
commit a85149c40e
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/overview_ring.rst
View File

@ -103,10 +103,14 @@ meta string A general-use field for storing additional information for the
====== ======= ============================================================== ====== ======= ==============================================================
Note: The list of devices may contain holes, or indexes set to None, for Note: The list of devices may contain holes, or indexes set to None, for
devices that have been removed from the cluster. Generally, device ids are not devices that have been removed from the cluster. However, device ids are
reused. Also, some devices may be temporarily disabled by setting their weight reused. Device ids are reused to avoid potentially running out of device id
to 0.0. To obtain a list of active devices (for uptime polling, for example) slots when there are available slots (from prior removal of devices). A
the Python code would look like: ``devices = list(self._iter_devs())`` consequence of this device id reuse is that the device id (integer value) does
not necessarily correspond with the chronology of when the device was added to
the ring. Also, some devices may be temporarily disabled by setting their
weight to 0.0. To obtain a list of active devices (for uptime polling, for
example) the Python code would look like: ``devices = list(self._iter_devs())``
************************* *************************
Partition Assignment List Partition Assignment List