Description of problem: Geo-replication CPU usage is 100% without any I/O. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Start Geo-replication and watch CPU usage. Actual results: CPU usage is 100% Expected results: CPU usage should not be 100%
REVIEW: http://review.gluster.org/13645 (geo-rep: Fix CPU utilization 100% with Popen) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/13645 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit c249931f2ca37d56391e671b37479555fec92686 Author: Aravinda VK <avishwan> Date: Tue Mar 8 13:41:58 2016 +0530 geo-rep: Fix CPU utilization 100% with Popen Errorstore is maintained by Geo-rep to collect errors from the child processes opened using Popen. If Popen.communicate is used then it closes stderr. When stderr is not available errorstore.tailer() will enter into infinite loop without gap. With this patch, sleep time added when stderr of Child process is already closed. Change-Id: Ic36aabd6de35b259467d0bab7952468432867a94 BUG: 1315582 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/13637 Reviewed-on: http://review.gluster.org/13645 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.9, please open a new bug report. glusterfs-3.7.9 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user