There are a lot of data that ceilometer collects. That data set is really huge, because it contains metrics related to ALL openstack components (and it's not only keystone notifications). And it's normal thing that we have a lot of data written during one day.
For that issues we have possible workarounds. First is time to live and ceilometer expirer. They was implemented as fix for https://bugs.launchpad.net/fuel/+bug/1399164 . Next workaround is described here https://bugs.launchpad.net/fuel/+bug/1434589 (please, pay attention on this comment https://bugs.launchpad.net/fuel/+bug/1434589/comments/15).
The main point is do not use requests for all meters (I mean "ceilometer meter-list") we should use timeouts, queries and etc.
There are a lot of data that ceilometer collects. That data set is really huge, because it contains metrics related to ALL openstack components (and it's not only keystone notifications). And it's normal thing that we have a lot of data written during one day. /bugs.launchpad .net/fuel/ +bug/1399164 . Next workaround is described here https:/ /bugs.launchpad .net/fuel/ +bug/1434589 (please, pay attention on this comment https:/ /bugs.launchpad .net/fuel/ +bug/1434589/ comments/ 15).
For that issues we have possible workarounds. First is time to live and ceilometer expirer. They was implemented as fix for https:/
The main point is do not use requests for all meters (I mean "ceilometer meter-list") we should use timeouts, queries and etc.
So, I mark this bug as invalid.