Poller tries to batch all samples in one message

Bug #1770310 reported by Sam Morrison
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Fix Released
Undecided
Sam Morrison

Bug Description

We've been looking into the central agent and have found some issues running in a large environment.

Currently if batch_polled_samples=True (default) then it will batch up all samples of a poller into one message. This can be problematic if the poller returns a large number of samples.

We are hitting this for the swift pollers as we have over 10k projects and it's trying to fix this in one message. Turning batch_polled_samples off fixes this but it means over 10k messages. Ideally there would be a setting to set a batch size

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ceilometer (master)

Fix proposed to branch: master
Review: https://review.openstack.org/567464

Changed in ceilometer:
assignee: nobody → Sam Morrison (sorrison)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ceilometer (master)

Reviewed: https://review.openstack.org/567464
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=2dc21a5f05ee670292a8a7f97952d3942c32f5cf
Submitter: Zuul
Branch: master

commit 2dc21a5f05ee670292a8a7f97952d3942c32f5cf
Author: Sam Morrison <email address hidden>
Date: Thu May 10 13:52:04 2018 +1000

    Ability to define batch size off polled samples.

    Currently if batch_polled_samples=True (default) then it will batch
    up all samples of a poller into one message. This can be problematic
    if the poller returns a large number of samples.

    Change-Id: Ifc60a0cb81876f6d9054cae82ba6579707a02f67
    Closes-bug: #1770310

Changed in ceilometer:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ceilometer 11.0.0

This issue was fixed in the openstack/ceilometer 11.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.