[fuel-library] Ceilometer's mongoDB is rapidly eating up partition space
Bug #1399164 reported by
Michael Polenchuk
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Ivan Berezovskiy | ||
5.1.x |
Won't Fix
|
High
|
Ivan Berezovskiy | ||
6.0.x |
Fix Committed
|
High
|
Ivan Berezovskiy | ||
6.1.x |
Fix Released
|
High
|
Ivan Berezovskiy |
Bug Description
Description of the environment:
Ceilometer with mongodb as backend
Steps to reproduce:
run in production environment
Expected result:
* time_to_live is configured ( N seconds > 0 )
* ceilometer-expirer is enabled to wipe out outdated metrics from database
Actual result:
ceilometer-expirer is disabled
Workaround:
Set time_to_live option in ceilometer.conf
and activate cron periodic expirer task
Impact:
Ceilometer collects quite huge amounts of metrics which keep in the database forever
In fuel 7.0 this should be done using native mongodb feature (as it's support was introduced in early kilo upstream code).
Changed in fuel: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 6.1 |
assignee: | nobody → Fuel Library Team (fuel-library) |
tags: | added: low-hanging-fruit |
tags: | added: release-notes |
description: | updated |
Changed in fuel: | |
status: | Triaged → In Progress |
no longer affects: | fuel/7.0.x |
tags: |
added: release-notes-done removed: release-notes |
To post a comment you must log in.
There is currently no best practice solution and we are too close to release of 6.0 right now. So we are putting this into release notes.
In order to apply a fix, user needs to setup cron job for ceilomter-expirer script and change time_to_live parameter to desired value in ceilometer.conf. After that he will need to restart collector service on all the controllers:
On CentOS:
/etc/init. d/openstack- ceilometer- collector restart
On Ubuntu:
/etc/init. d/ceilometer- collector restart
But user should be aware that all the old data will still be created with old ttl value, so if he needs he will need to wipe the data himself.