shredding LVM volumes may affect performance of other VMs on compute host
Bug #1835201 reported by
Pavlo Shchelokovskyy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
When configured with LVM local storage for ephemeral partitions, Nova performs wiping operation using `shred` before removing volume once a VM is deleted.
`shred` consumes a lot of CPU and almost all disk bandwidth (even on SSDs) which drastically affects the performance of other VMs running on the same Compute.
The bigger volume size is specified in a flavor the longer this operation takes and VMs suffer.
Would be nice to be able to specify the ionice level for this operation (like `ionice -c3` to use the Idle I/O Scheduler).
To post a comment you must log in.
Cinder has a config option for specifying ionice:
https:/ /github. com/openstack/ cinder/ blob/db88f0a15e 75b01c0073fb4d1 850420d797b9a3b /cinder/ volume/ driver. py#L78
I could see the same thing being added to nova.