[Bugs] [Bug 1286346] Data Tiering:Don't allow or reset the frequency threshold values to zero when record counter features.record-counter is turned off

[bugzilla at redhat.com]

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



--- Comment #11 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12780 committed in master by Dan Lambright
(dlambrig at redhat.com) 
------
commit eea50e82365770dea56cdddca89cd6d3b8bb7a22
Author: Joseph Fernandes <josferna at redhat.com>
Date:   Sat Nov 28 17:03:41 2015 +0530

    tier/glusterd : Validation for frequency thresholds and record-counters

    1) if record-counters is set to off
       check if both the frequency thresholds are non-zero, then pop
       an error message, with volume set failed.
    2) if record-counters is set to on
       check if both the frequency thresholds are zero, then pop
       an note, but volume set is not failed.
    3) If any of the frequency thresholds are set to a non-zero value,
       switch record-counters on, if not already on
    4) If both the frequency thresholds are set to zero,
       switch record-counters off, if not already off

    NOTE: In this fix we have
    1) removed unnecessary ctr vol set options.
    2) changed  ctr_hardlink_heal_expire_period to ctr_lookupheal_link_timeout

    Change-Id: Ie7ccfd3f6e021056905a79de5a3d8f199312f315
    BUG: 1286346
    Signed-off-by: Joseph Fernandes <josferna at redhat.com>
    Signed-off-by: Dan Lambright <dlambrig at redhat.com>
    Reviewed-on: http://review.gluster.org/12780
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>

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