[Bugs] [Bug 1366648] [GSS] A hot tier brick becomes full, causing the entire volume to have issues and returns stale file handle and input /output error.

bugzilla at redhat.com bugzilla at redhat.com
Wed Oct 19 19:51:54 UTC 2016


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



--- Comment #15 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15158 committed in master by Dan Lambright
(dlambrig at redhat.com) 
------
commit 460016428cf27484c333227f534c2e2f73a37fb1
Author: Milind Changire <mchangir at redhat.com>
Date:   Sat Oct 15 10:49:19 2016 +0530

    cluster/tier: handle fast demotions

    Demote files on priority if hi-watermark has been breached and continue
    to demote until the watermark drops below hi-watermark.

    Monitor watermark more frequently.
    Trigger demotion as soon as hi-watermark is breached.
    Add cluster.tier-emergency-demote-query-limit option to limit number
    of files returned from the database query for every iteration of
    tier_migrate_using_query_file(). If watermark hasn't dropped below
    hi-watermark during the first iteration, the next iteration will be
    triggered approximately 1 second after tier_demote() returns to the
    main tiering loop.
    Update changetimerecorder xlator to handle query for emergency demote
    mode.

    Add tier-ctr-interface.h:
    Move tier and ctr interface specific macros and struct definition from
    libglusterfs/src/gfdb/gfdb_data_store.h to new header
    libglusterfs/src/tier-ctr-interface.h

    Change-Id: If56af78c6c81d37529b9b6e65ae606ba5c99a811
    BUG: 1366648
    Signed-off-by: Milind Changire <mchangir at redhat.com>
    Reviewed-on: http://review.gluster.org/15158
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: 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.


More information about the Bugs mailing list