From a000d47ed172718ed72f9a62db9ae00b3b0c1644 Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Wed, 1 Nov 2017 10:09:22 -0700 Subject: [PATCH] Disable crm114 on the logstash worker nodes The logstash worker nodes are running out of disk because crm114 has enough unique files to process that at 13MB per file we are still filling up many gigabytes of data and filling out disks. We will need to work on collapsing files (perhaps not use their full path and just use their basename?) and work to eliminate log files that are unique like those that have the hostname in them (as this means we create a new file for every job run). Change-Id: Ie729a3d2628f0ded65574c267e31c14f6b795b29 --- .../templates/logstash/jenkins-log-worker.yaml.erb | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/modules/openstack_project/templates/logstash/jenkins-log-worker.yaml.erb b/modules/openstack_project/templates/logstash/jenkins-log-worker.yaml.erb index 263b5e24c3..c41eeede3a 100644 --- a/modules/openstack_project/templates/logstash/jenkins-log-worker.yaml.erb +++ b/modules/openstack_project/templates/logstash/jenkins-log-worker.yaml.erb @@ -3,8 +3,9 @@ gearman-port: 4730 output-host: localhost output-port: 9999 output-mode: tcp -crm114-script: /usr/local/bin/classify-log.crm -crm114-data: /var/lib/crm114 +# Temporarily disabled as this is filling our worker node disks +#crm114-script: /usr/local/bin/classify-log.crm +#crm114-data: /var/lib/crm114 mqtt-host: <%= @mqtt_hostname %> mqtt-port: <%= @mqtt_port %> mqtt-topic: gearman-logstash/<%= @hostname %>