Allow Swift fallocate_reserve to be set per service
Bug #1545018 reported by
Andy McCrae
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Andy McCrae | ||
Kilo |
Won't Fix
|
Undecided
|
Unassigned | ||
Liberty |
Fix Committed
|
Medium
|
Kevin Carter | ||
Trunk |
Fix Released
|
High
|
Andy McCrae |
Bug Description
When swift drives fill up completely it becomes difficult to administrate - you can't delete objects since this requires a write (of a tombstone file).
There is a built in fallocate_reserve value (per service) that will allow a set amount of space to be seen as "full", by the swift storage services, without actually being in use.
We should expose this value and default it to something smallish (e.g. 10GB since max swift write is 5GB).
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/279589
Review: https:/