[Bugs] [Bug 1287560] 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
bugzilla at redhat.com
Wed Dec 2 19:47:21 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1287560
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12849 committed in release-3.7 by Dan
Lambright (dlambrig at redhat.com)
------
commit 06b7ca1dcd7f3c3187e83a17fad7224d661b4d7e
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
Backport of http://review.gluster.org/12780
> 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>
> Signed-off-by: Joseph Fernandes <josferna at redhat.com>
Change-Id: I35621ed3cc1ad20a75ef16e0b95453b8c6120852
BUG: 1287560
Signed-off-by: Joseph Fernandes <josferna at redhat.com>
Reviewed-on: http://review.gluster.org/12849
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Dan Lambright <dlambrig at redhat.com>
Tested-by: Dan Lambright <dlambrig at redhat.com>
--
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.
More information about the Bugs
mailing list