[Bugs] [Bug 1501023] Make choose-local configurable through `volume-set` command

bugzilla at redhat.com bugzilla at redhat.com
Tue Apr 24 09:37:00 UTC 2018


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

Vijay Avuthu <vavuthu at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED



--- Comment #8 from Vijay Avuthu <vavuthu at redhat.com> ---
Update:
==========

Build used : glusterfs-3.12.2-8.el7rhgs.x86_64


Verified with below scenarios:

Scenario 1:

1) create 1 * 3 replicate volume ( each brick on different node: N1, N2 and N3
) and start
2) write file from the mount point
3) start volume profile
4) mount the volume on N1
5) clear the volume profile
6) read the file from N1 mount point
7) check profile info
8) set cluster.choose-local to off
9) clear the volume profile
10) read the file from N1 mount point
11) check profile info

below is o/p after step 11, STAT call goes to b2 which is expected when we
choose-local to off

# gluster vol profile 13 info 
Brick: 10.70.35.61:/bricks/brick2/b0
------------------------------------
Cumulative Stats:
 %-latency   Avg-latency   Min-Latency   Max-Latency   No. of calls         Fop
 ---------   -----------   -----------   -----------   ------------        ----
    100.00     302.00 us     302.00 us     302.00 us              1      LOOKUP

    Duration: 32 seconds
   Data Read: 0 bytes
Data Written: 0 bytes

Interval 1 Stats:
 %-latency   Avg-latency   Min-Latency   Max-Latency   No. of calls         Fop
 ---------   -----------   -----------   -----------   ------------        ----
    100.00     302.00 us     302.00 us     302.00 us              1      LOOKUP

    Duration: 26 seconds
   Data Read: 0 bytes
Data Written: 0 bytes

Brick: 10.70.35.174:/bricks/brick2/b1
-------------------------------------
Cumulative Stats:
 %-latency   Avg-latency   Min-Latency   Max-Latency   No. of calls         Fop
 ---------   -----------   -----------   -----------   ------------        ----
     35.22     236.00 us     236.00 us     236.00 us              1        STAT
     64.78     434.00 us     434.00 us     434.00 us              1      LOOKUP

    Duration: 32 seconds
   Data Read: 0 bytes
Data Written: 0 bytes

Interval 1 Stats:
 %-latency   Avg-latency   Min-Latency   Max-Latency   No. of calls         Fop
 ---------   -----------   -----------   -----------   ------------        ----
     35.22     236.00 us     236.00 us     236.00 us              1        STAT
     64.78     434.00 us     434.00 us     434.00 us              1      LOOKUP

    Duration: 26 seconds
   Data Read: 0 bytes
Data Written: 0 bytes

Brick: 10.70.35.17:/bricks/brick2/b2
------------------------------------
Cumulative Stats:
   Block Size:                 16b+ 
 No. of Reads:                    1 
No. of Writes:                    0 
 %-latency   Avg-latency   Min-Latency   Max-Latency   No. of calls         Fop
 ---------   -----------   -----------   -----------   ------------        ----
     13.94     256.00 us     256.00 us     256.00 us              1       FSTAT
     34.30     630.00 us     630.00 us     630.00 us              1      LOOKUP
     51.77     951.00 us     951.00 us     951.00 us              1        READ

    Duration: 32 seconds
   Data Read: 24 bytes
Data Written: 0 bytes

Interval 1 Stats:
   Block Size:                 16b+ 
 No. of Reads:                    1 
No. of Writes:                    0 
 %-latency   Avg-latency   Min-Latency   Max-Latency   No. of calls         Fop
 ---------   -----------   -----------   -----------   ------------        ----
     13.94     256.00 us     256.00 us     256.00 us              1       FSTAT
     34.30     630.00 us     630.00 us     630.00 us              1      LOOKUP
     51.77     951.00 us     951.00 us     951.00 us              1        READ

    Duration: 26 seconds
   Data Read: 24 bytes
Data Written: 0 bytes
# 


scenario : 2

1) create 1 * 3 replicate volume ( each brick on different node: N1, N2 and N3
) and start
2) write file from the mount point
3) on N2 and N3, modify the data ( file should be same size as N1 ) from
backend
4) mount the volume on N1
6) read the file from N1 mount point 
8) set cluster.choose-local to off
9) unmount and mount the volume on N1 again 
10) read the file from N1 mount point 

>From N1 :

# cat file
Test choos-local option
#

>From N2 :

[root at dhcp35-174 b1]# cat file
Fqwe 12345-12345 option
# 

>From N3 :
# cat file
Fqwe 12345-12345 option
# 

> o/p of Reading file after step 10

# cat /mnt/13/file
Fqwe 12345-12345 option
# 

Changing status to Verified.

-- 
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=3ViC8Nbj1G&a=cc_unsubscribe


More information about the Bugs mailing list