Bug 1315601 - Geo-replication CPU usage is 100%
Geo-replication CPU usage is 100%
Product: GlusterFS
Classification: Community
Component: geo-replication (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Aravinda VK
Depends On: 1315582
  Show dependency treegraph
Reported: 2016-03-08 03:16 EST by Aravinda VK
Modified: 2016-06-16 09:59 EDT (History)
2 users (show)

See Also:
Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1315582
Last Closed: 2016-06-16 09:59:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aravinda VK 2016-03-08 03:16:37 EST
+++ 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%
Comment 1 Vijay Bellur 2016-03-08 03:17:38 EST
REVIEW: http://review.gluster.org/13637 (geo-rep: Fix CPU utilization 100% with Popen) posted (#1) for review on master by Aravinda VK (avishwan@redhat.com)
Comment 2 Vijay Bellur 2016-03-08 08:53:52 EST
COMMIT: http://review.gluster.org/13637 committed in master by Jeff Darcy (jdarcy@redhat.com) 
commit 4318354aac650c18b4047142e43f3d4cff4310a7
Author: Aravinda VK <avishwan@redhat.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.
    Change-Id: Ic36aabd6de35b259467d0bab7952468432867a94
    BUG: 1315601
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13637
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Comment 3 Niels de Vos 2016-06-16 09:59:45 EDT
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

Note You need to log in before you can comment on or make changes to this bug.