Red Hat Bugzilla – Bug 1559432
Before import cluster monitoring integration consumes lot of CPU and memory
Last modified: 2018-09-04 03:03:21 EDT
Description of problem: Monitoring-integration sync-interval time is fetched from gluster_ns in central-store. But before cluster import gluster_ns is not created in central store. So monitoring-integration sync thread is keep executed without any break, So it consumes a lot of CPU and memory resources. Version-Release number of selected component (if applicable): How reproducible: Install and start monitoring-integration before import cluster and check CPU and memory resource consumption. Steps to Reproduce: 1. 2. 3. Actual results: monitoring-integration consumes a lot of CPU and memory Expected results: monitoring-integration should consume less CPU and memory Additional info:
Could you provide more details about: * Version where the bug is present. * Is it possible to reproduce this on previously released RHGS WA? * Link to upstream merge request.
It is possible to reproduce in all previous released RHGS, After executing ansible script for installing tendrl components, check the CPU and memory resource consumption using a command top.
Check cpu and memory resource which is used by monitoring-integration in server node, it is reproducible in rhgs 1.6.1-1
sorry, In version 3.3.1 it can be reproducible
I meant 1.6.1-1 is actually RHGS-WA NVR 1.6.1-1
Reproduced on tendrl-monitoring-integration-1.6.1-1.el7rhgs.noarch.
Tested and verified on tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch. CPU and memory consumption of tendrl-monitoring-integration service is constantly bellow 1%. # ps -p $(echo $(ps aux | grep [t]endrl-monitoring-integration | awk '{print $2}') | sed 's/ /,/') -o %cpu,%mem,cmd -h; 0.4 0.3 /usr/bin/python /usr/bin/tendrl-monitoring-integration >> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2616