[Bugs] [Bug 1448790] [Tiering]: High and low watermark values when set to the same level, is allowed

bugzilla at redhat.com bugzilla at redhat.com
Fri May 12 19:58:29 UTC 2017


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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17202 committed in release-3.10 by
Raghavendra Talur (rtalur at redhat.com) 
------
commit e07337d56ea91e75c48ccdc8c386ce892969ca62
Author: hari gowtham <hgowtham at redhat.com>
Date:   Thu May 4 15:49:59 2017 +0530

    Tier: Watermark check for hi and low value being equal

            back-port of : https://review.gluster.org/17175

    Problem: Both low and hi watermark can be set to same value
    as the check missed the case for being equal.

    Fix: Add the check to both the hi and low values being equal
    along with the low value being higher than hi value.

    >Change-Id: Ia235163aeefdcb2a059e2e58a5cfd8fb7f1a4c64
    >BUG: 1447960
    >Signed-off-by: hari gowtham <hgowtham at redhat.com>
    >Reviewed-on: https://review.gluster.org/17175
    >Smoke: Gluster Build System <jenkins at build.gluster.org>
    >Tested-by: hari gowtham <hari.gowtham005 at gmail.com>
    >Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    >Reviewed-by: Milind Changire <mchangir at redhat.com>
    >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

    Change-Id: Ia235163aeefdcb2a059e2e58a5cfd8fb7f1a4c64
    BUG: 1448790
    Signed-off-by: hari gowtham <hgowtham at redhat.com>
    Reviewed-on: https://review.gluster.org/17202
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005 at gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj 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.


More information about the Bugs mailing list