[Bugs] [Bug 1231516] New: glusterfsd process on 100% cpu, upcall busy loop in reaper thread

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1231516

            Bug ID: 1231516
           Summary: glusterfsd process on 100% cpu, upcall busy loop in
                    reaper thread
           Product: GlusterFS
           Version: 3.7.1
         Component: upcall
          Keywords: Triaged
          Severity: high
          Priority: high
          Assignee: ndevos at redhat.com
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org, skoduri at redhat.com
        Depends On: 1200267
            Blocks: 1227206 (glusterfs-3.7.2)



Description of problem:

http://review.gluster.org/10342 introduced a cleanup thread for expired client
entries. When enabling the 'features.cache-invalidation' volume option, the
brick process starts to run in a busy-loop. Obviously this is not intentional,
and a process occupying 100% of the cycles on a CPU or core is not wanted.

Version-Release number of selected component (if applicable):
glusterfs 3.7.1

How reproducible:
always

Steps to Reproduce:
1. enable the upcall xlator with
     # gluster volume set $VOLNAME features.cache-invalidation on

Actual results:
The glusterfsd processes start to run with 100% cpu usage.

Expected results:
Minimal/no impact on the glusterfsd processes.

Additional info:
Needs backport of http://review.gluster.org/11198


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1200267
[Bug 1200267] Upcall: Cleanup the expired upcall entries
https://bugzilla.redhat.com/show_bug.cgi?id=1227206
[Bug 1227206] GlusterFS 3.7.2 tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EMNTVy0lmY&a=cc_unsubscribe