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

[bugzilla at redhat.com]

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

SATHEESARAN <sasundar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amukherj at redhat.com,
                   |                            |sasundar at redhat.com
              Flags|                            |needinfo?(amukherj at redhat.c
                   |                            |om)



--- Comment #1 from SATHEESARAN <sasundar at redhat.com> ---
I think the barrier option is turned off internally when barrier-timeout is
met, but not reflected anywhere else.

If you take a brick statedump ( by using gluster volume statedump <volname> all
), you can see that barrier is turned off after barrier-timeout seconds
# gluster volume statedump <vol> all
# grep barrier.enabled
/var/run/gluster/<brickpath>.<brick-pid>.dump.<timestamp>

Since the state of barrier is not restored in volume options, volume get is
also returning the old value which is 'enable', but its actually disabled

Atin, do you think the state of barrier should be dynamically obtained from
'gluster volume get' ?

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