container partitions directories never removed
Bug #1396152 reported by
Caleb Tennis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Looks like was thought to be originally fixed in https:/
The issue with this is that the container replicator loops over the partitions directories during the start of a run, so having a ton of empty directories across many disks really degrades performance of the run.
(This may be also be a problem for accounts too, I'm not entire sure).
Changed in swift: | |
milestone: | none → 2.2.1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/138524 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=d40cebfe55a 2ef63e0fdceb215 48587bad497a69
Committed: https:/
Submitter: Jenkins
Branch: master
commit d40cebfe55a2ef6 3e0fdceb2154858 7bad497a69
Author: Caleb Tennis <email address hidden>
Date: Tue Dec 2 15:28:26 2014 -0500
Clean up empty account and container partitions directories.
Because we iterate over these directories on a replication run,
and they are not (previously) cleaned up, the time to start the
replication increases incrementally for each stale directory
lying around. Thousands of directories across dozens of disks
on a single machine can make for non-trivial startup times.
Plus it just seems like good housekeeping.
Closes-Bug: #1396152
Change-Id: Iab607b03b7f011 e87b799d1f9af7a b3b4ff30019