[Bugs] [Bug 1318068] New: features.barrier is not set to "disable" after barrier timeout expires

[bugzilla at redhat.com]

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

            Bug ID: 1318068
           Summary: features.barrier is not set to "disable" after barrier
                    timeout expires
           Product: GlusterFS
           Version: 3.7.9
         Component: barrier
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: jack.wong at laserfiche.com
                CC: bugs at gluster.org



Description of problem:
If a volume's barrier is removed because the barrier timeout expires, the
volume options still show the barrier as being enabled.

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

How reproducible:
Always

Steps to Reproduce:
1. Enable the barrier on a volume. (gluster volume barrier VOLUME enable)
2. Wait for the barrier timeout to expire. By default, this is two minutes. To
see the number of seconds required, run "gluster volume get VOLUME
features.barrier-timeout".

Actual results:
Running "gluster volume get VOLUME features.barrier" shows that the barrier is
still enabled, but the barrier has been automatically disabled by Gluster.

Expected results:
The barrier should be shown as disabled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.