[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|                            |jack.wong at laserfiche.com
              Flags|                            |needinfo?(jack.wong at laserfi
                   |                            |che.com)



--- Comment #2 from SATHEESARAN <sasundar at redhat.com> ---
Jack,

You have 2 options to check whether barrier is enabled.

1. Get the volume statedump and grep for 'barrier.enabled'
[root@ ~]# grep barrier.enabled
/var/run/gluster/rhs-brick1-b1.28902.dump.1458098783 
barrier.enabled=0

2. Check for brick logs ( /var/log/glusterfs/bricks/* )
[root@ ~]# grep -i 'barrier timeout'
/var/log/glusterfs/bricks/rhs-brick1-b1.log 
[2016-03-16 03:23:51.353413] C [barrier.c:409:barrier_timeout] 0-test-barrier:
Disabling barrier because of the barrier timeout.

I am also curious the reason behind using barrier directly.
What is the requirement behind it ?

For your infromation, barrier is indirectly internally called by snapshot
feature, while snapshot is taken.

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