[Bugs] [Bug 1242504] [Data Tiering]: Frequency Counters of un-selected file in the DB wont get clear after a promotion/demotion cycle

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11648 committed in master by Dan Lambright
(dlambrig at redhat.com) 
------
commit b5a98df6343da6229b1b102883d8e992cd4a55a5
Author: Joseph Fernandes <josferna at redhat.com>
Date:   Mon Jul 13 18:45:11 2015 +0530

    tier/libgfdb : Setting Freq counters of un-selected files to zero

    Change Time Recorder increments the write/read frequency counters
    on a read or write of a file, if the "features.record-counters" is
    "on". It is the responsibility of the tiering migrator to reset
    these counters to zero for un-selected files to reset them to zero
    as frequency counters are function of promotion/Demotion cycles.
    If the counters are not set to zero then,

    1) the counters may overflow in the DB
    2) The file may be wrongly promoted or demoted.

    This fix will reset the freq counters of un-selected files to zero
    after promotion/demotion frequency.

    Change-Id: Ideea2c76a52d421a7e67c37fb0c823f552b3da7a
    BUG: 1242504
    Signed-off-by: Joseph Fernandes <josferna at redhat.com>
    Reviewed-on: http://review.gluster.org/11648
    Tested-by: Joseph Fernandes
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-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.