duplicated pipeline support meter check when publish samples
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Invalid
|
Low
|
Wenzhi Yu | ||
Juno |
Won't Fix
|
Low
|
Wenzhi Yu | ||
Kilo |
Won't Fix
|
Low
|
Wenzhi Yu |
Bug Description
see[1], when publishing sample with sample pipeline, it will check the samples supported by the source definition of the pipeline or not, but the samples is always supported by this pipeline, because when setup polling tasks, the pollster has been checked and matched corresponding pipeline, see[2]. so the samples from the pollsters is always supported by the pipeline. this check has no affect of the publishing result, but will cost cpu resources if we have a complex pipeline definition.
[1] https:/
[2] https:/
this bug affect Kilo and Juno
no longer affects: | ceilometer (Ubuntu) |
tags: | added: kilo |
tags: | removed: kilo |
description: | updated |
Changed in ceilometer: | |
assignee: | nobody → Wen Zhi Yu (yuywz) |
Changed in ceilometer: | |
status: | New → In Progress |
Changed in ceilometer: | |
assignee: | Wen Zhi Yu (yuywz) → Rohit Jaiswal (rohit-jaiswal-3) |
Changed in ceilometer: | |
assignee: | Rohit Jaiswal (rohit-jaiswal-3) → Wen Zhi Yu (yuywz) |
Changed in ceilometer: | |
importance: | Undecided → Low |
status: | In Progress → Invalid |
I think the check is necessary in Liberty code. Please see my comment at https:/ /review. openstack. org/#/c/ 222504/, so please mark this only affect kilo/juno branch