| 2016-10-13 19:22:49 |
gordon chung |
description |
list_metric_with_measures_to_process lists all the metrics available to be processed. it grabs the first x items from the resultset. the order of resultset is not controlled right now and is dictated by backend. it's very common if you don't have a fast enough processing rate or enough large enough amount of workers that certain metrics will never be processed as it will always get pushed back in line by other metrics. this for sure happens in ceph.
it'd be nice if list_metric_with_measures_to_process returned back based on earliest time unprocessed measures were add. that way, we could fairly process all measures without having to resort to high processing rate
work around is to always use 'refresh=True' on query so you guarantee latest.
i think this is a bug.. and a complicated bug... but possibly low priority since there's workaround. |
list_metric_with_measures_to_process lists all the metrics available to be processed. it grabs the first x items from the resultset. the order of resultset is not controlled right now and is dictated by backend. it's very common if you don't have a fast enough processing rate or large enough amount of workers that certain metrics will never be processed as it will always get pushed back in line by other metrics. this for sure happens in ceph.
it'd be nice if list_metric_with_measures_to_process returned back based on earliest time unprocessed measures were add. that way, we could fairly process all measures without having to resort to high processing rate
work around is to always use 'refresh=True' on query so you guarantee latest.
i think this is a bug.. and a complicated bug... but possibly low priority since there's workaround. |
|
