nova-api consumes more memory which causes OOM on controller nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Oleksiy Molchanov |
Bug Description
With provided nova packages version: 13.0.0-
1. `soft-deleted` instances are kept inside the database which is leading to a situation that DB is really huge and needs to be cleaned by that solution: https:/
2. nova-api memory grows over time and even if we will execute that recommendation from point 1 it seems it's not reclaiming memory and it leads to nova-api crash by OOM when host memory is exhausted -> that looks like a blocker from a customer perspective as it can lead to some issues with already on-going nova operations. So restart from time to time is not acceptable by the customer, even if it’s a part of workaround.
If we have a solution which is released in a newer version of Mitaka for Nova, it would be nice to mention, currently, I was not able to find that, but customer version of nova is pretty old. Additionally, the customer has some specific version which was compacted by them.
Changed in fuel: | |
assignee: | nobody → Oleksiy Molchanov (omolchanov) |
Changed in fuel: | |
status: | New → In Progress |
importance: | Undecided → Medium |
milestone: | none → 9.2-mu-12 |
We need to consider backporting of https:/ /review. openstack. org/#/c/ 409943/