From 108a46421468a196bcdcc7f7c9e0c9f84e7af458 Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Sat, 29 Dec 2012 08:40:14 -0800 Subject: [PATCH] Work acound carbon issue #55. grahpite.o.o currently has a manually installed fix for carbon issue #55 in place, but in case we lose that, setting MAX_CPM to >=60 should work around the problem. https://github.com/graphite-project/carbon/issues/55 Change-Id: I53bbe348737edc0c513bb1b34b753018d20c3d60 Reviewed-on: https://review.openstack.org/18750 Reviewed-by: Jeremy Stanley Approved: Clark Boylan Reviewed-by: Clark Boylan Tested-by: Jenkins --- modules/graphite/templates/carbon.conf.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/graphite/templates/carbon.conf.erb b/modules/graphite/templates/carbon.conf.erb index 4cab857db6..3256accead 100644 --- a/modules/graphite/templates/carbon.conf.erb +++ b/modules/graphite/templates/carbon.conf.erb @@ -55,7 +55,7 @@ MAX_UPDATES_PER_SECOND = 500 # database files to all get created and thus longer until the data becomes usable. # Setting this value high (like "inf" for infinity) will cause graphite to create # the files quickly but at the risk of slowing I/O down considerably for a while. -MAX_CREATES_PER_MINUTE = 50 +MAX_CREATES_PER_MINUTE = 60 LINE_RECEIVER_INTERFACE = 0.0.0.0 LINE_RECEIVER_PORT = 2003