+++ This bug was initially created as a clone of Bug #1315582 +++ 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/13637 (geo-rep: Fix CPU utilization 100% with Popen) posted (#1) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/13637 committed in master by Jeff Darcy (jdarcy) ------ commit 4318354aac650c18b4047142e43f3d4cff4310a7 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: 1315601 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/13637 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat> CentOS-regression: Gluster Build System <jenkins.com>
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.8.0, please open a new bug report. glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user