[Bugs] [Bug 1320412] disperse: Provide an option to enable/disable eager lock

[bugzilla at redhat.com]

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



--- Comment #5 from nchilaka <nchilaka at redhat.com> ---
FOllowing is the QATP for validating this bug.
TC#1 and TC#6 are the main cases which are expected to pass so as to confirm
that the fix is working
TC#1,2,3,7 are CLI validation
TC#4,5 are to check for regressing of the options
TC#6 is the main case to validate if the fix is really working

QATP:

    TC#1: User must be able to enable/disable eager lock option on an EC volume 

    1.Create an EC volume and start it

    2. Now try to enable disperse eager lock on the volume using  gluster v set
<VOLUME NAME> disperse.eager-lock on      

    3. Now get the options of volume and check fo the above option

    The option must be enabled on the volume

    4. Now disable the option using  gluster v set <VOLUME NAME>
disperse.eager-lock off

    The option must get disabled


    TC#2: by default EC volume must have disperse.eager-lock enabled

    1.Create an EC volume and start it

    2.Now get the options of volume and check fo the disperse.eager-lock 
option

    The option must be enabled on the volume by default


    TC#3: by default EC volume must have disperse.eager-lock enabled

    1.Create an EC volume and start it

    2.Now get the options of volume and check fo the disperse.eager-lock 
option

    The option must be enabled on the volume by default



    TC#4: AFR Eager lock must not have effect on  EC volume

    1.Create an EC volume and start it

    2.Now set the eager lock option meant for AFR volume on EC volume by
turning on cluster.eager-lock

    The option must not be allowed--->but this works will file a bug

    3.Now mount the volume and use dd command to create a 1GB file

    4. Keep viewing the profile of the volume.

    Expected behavior: The INODELK count must keep increasing rapidly


    TC#5: EC Eager lock must not have effect on  AFR volume

    1.Create an AFR volume and start it

    2.Now set the eager lock option meant for EC volume on AFR volume by
turning on disperse.eager-lock

    The option must not be allowed--->but this works will file a bug

    3.Now mount the volume and use dd command to create a 1GB file

    4. Keep viewing the profile of the volume.

    Expected behavior: The INODELK count must keep increasing rapidly


    TC#6: Eager lock Functional validation: Eager lock must reduce the number
of locks being taken when writing to the file continuosly

    1.Create an AFR volume and start it

    2.Now set the eager lock option  by turning on disperse.eager-lock

    3.Now mount the volume and use dd command to create a 1GB file

    4. Keep viewing the profile of the volume.

    Expected behavior: The INODELK count must be incrementing at a very low
pace, may be in total there must be about 10 locks for each brick(when compared
to when options is turned off with inodelk being in range of about 9000)


    TC#7: CLI sanity of disperse eager lock

    1.Create an EC volume

    2.Now try to set the eager lock option  by turning on disperse.eager-lock
by using different inputs. 

    Only booleans like 1 or 0 true or false and on/off must be allowed

    3. try to enable the option on already enabled volume

    It must fail, saying it is already enabled

    4. Try to disable on already disable volume

    It must fail, saying it is already disabled

    5. check for the help

    the help must have sufficent data to be useful

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