openstack/kolla-ansible
Code Issues Proposed changes

Support configuring Monasca Persister performance

Browse Source 
On a single node deployment, the Monasca persister can
limit the rate at which Monasca can persist metrics to
InfluxDB. Increasing the thread count can remove this
bottle neck.

Partially-Implements: blueprint monasca-roles
Change-Id: I763a5ae6aa8c8ab3bf766ab5b58c386da74a188b
This commit is contained in:
Doug Szumski 2018-09-25 11:03:16 +00:00
parent 6b4cd657ad
commit 9c2e0b81d5
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
ansible/roles/monasca/defaults/main.yml
View File

@ -123,6 +123,7 @@ monasca_periodic_notifications_period: 60
# the total number of threads across all instances of a service does not # the total number of threads across all instances of a service does not
# exceed the Kafka topic partition count. # exceed the Kafka topic partition count.
monasca_log_pipeline_threads: 2 monasca_log_pipeline_threads: 2
monasca_metric_pipeline_threads: 2
#################### ####################
# Docker # Docker

2
ansible/roles/monasca/templates/monasca-persister/persister.conf.j2
View File

@ -17,7 +17,7 @@ num_processors = 1
[kafka_metrics] [kafka_metrics]
uri = {{ monasca_kafka_servers }} uri = {{ monasca_kafka_servers }}
topic = {{ monasca_metrics_topic }} topic = {{ monasca_metrics_topic }}
num_processors = 1 num_processors = {{ monasca_metric_pipeline_threads }}
[zookeeper] [zookeeper]
uri = {{ monasca_zookeeper_servers }} uri = {{ monasca_zookeeper_servers }}