<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div>Hello Bill </div><div><br></div><div>Possible to share how many instance and how many meter per instance you collecting and getting this error ? </div><div><br></div><div>I guess for scaling purpose , you are talking about this , right <a href="http://docs.openstack.org/ha-guide/controller-ha-telemetry.html">http://docs.openstack.org/ha-guide/controller-ha-telemetry.html</a> </div><div><br></div><div>Regards</div><div>VM</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Bill Jones <<a href="mailto:bill.jones@sungardas.com">bill.jones@sungardas.com</a>><br><span style="font-weight:bold">Date: </span> Tuesday 14 June 2016 at 18:03<br><span style="font-weight:bold">To: </span> "openstack-oper." <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br><span style="font-weight:bold">Subject: </span> [Openstack-operators] Scaling Ceilometer compute agent?<br></div><div><br></div><div dir="ltr"><div style="font-size:13px">Has anyone had any experience with scaling ceilometer compute agents?<br></div><div style="font-size:13px"><br></div><span style="font-size:13px">We're starting to see messages like this in logs for some of our compute agents:</span><div style="font-size:13px"><br></div><blockquote style="font-size:13px;margin:0px 0px 0px 40px;border:none;padding:0px"><div>WARNING ceilometer.openstack.common.loopingcall [-] task <function interval_task at 0x2092cf8> run outlasted interval by 293.25 sec</div><div><br></div></blockquote><span style="font-size:13px">This is an indication that the compute agent failed to execute its pipeline processing within the allotted interval (in our case 10 min). The result of this is that less instance samples are generated per hour than expected, and this causes billing issues for us due to the way we calculate usage. </span><div style="font-size:13px"><br></div><div style="font-size:13px">It looks like we have three options for addressing this: make the pipeline run faster, increase the interval time, or scale the compute agents. I'm investigating the latter.</div><div style="font-size:13px"><br></div><div style="font-size:13px">I think I read in the ceilometer architecture docs that the agents are designed to scale, but I don't see anything in the docs on how to facilitate that. Any pointers would be appreciated.</div><div style="font-size:13px"><br></div><div style="font-size:13px">Thanks,</div><div style="font-size:13px">Bill</div><div class="" style="margin:2px 0px 0px;font-size:13px"></div></div>
_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</span></body></html>