Red Hat Bugzilla – Bug 1315601
Geo-replication CPU usage is 100%
Last modified: 2016-06-16 09:59:45 EDT
+++ 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):
Steps to Reproduce:
Start Geo-replication and watch CPU usage.
CPU usage is 100%
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 (email@example.com)
COMMIT: http://review.gluster.org/13637 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Aravinda VK <email@example.com>
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.
Signed-off-by: Aravinda VK <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
Reviewed-by: Kotresh HR <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.