[Bugs] [Bug 1323017] Ordering query results from libgfdb

bugzilla at redhat.com bugzilla at redhat.com
Tue Apr 26 21:51:08 UTC 2016


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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13881 committed in release-3.7 by Dan
Lambright (dlambrig at redhat.com) 
------
commit 681d4590bd7e13b742c399573da55c509eb5b2a2
Author: Joseph Fernandes <josferna at redhat.com>
Date:   Fri Mar 4 08:55:09 2016 +0530

    tier/libgfdb: Ordering query results from libgfdb

    When querying we will order the query result to get
    the hotest or the coldest files in the queried list
    so that these files are migrated first.

    Now here we are giving priority to the write heat(time and counters),
    as it requires complex queries to have a composite
    ordering of write and read + it has it impact on performance.

    Backport of http://review.gluster.org/13607

    > Change-Id: I2e0415dcfad4218b42c68fc5c2ed8d1f075ce9ea
    > Signed-off-by: Joseph Fernandes <josferna at redhat.com>
    > Reviewed-on: http://review.gluster.org/13607
    > Smoke: Gluster Build System <jenkins at build.gluster.com>
    > Tested-by: Joseph Fernandes
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    > Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Signed-off-by: Joseph Fernandes <josferna at redhat.com>

    Change-Id: If5fad07f8d0f50016b10e256803abd5266cd708f
    BUG: 1323017
    Reviewed-on: http://review.gluster.org/13881
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Joseph Fernandes
    Tested-by: Joseph Fernandes
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    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.


More information about the Bugs mailing list