[Bugs] [Bug 1211863] RFE: Support in md-cache to use upcall notifications to invalidate its cache

[bugzilla at redhat.com]

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



--- Comment #93 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15314 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit 3f5273e19af2eaa7bc33c6abaf6b10850f97dcc0
Author: Poornima G <pgurusid at redhat.com>
Date:   Thu Aug 25 10:25:24 2016 +0530

    md-cache: Do not use features.cache-invalidation for both md-cache and
upcall

    Currently, the volume set option features.cache-invalidation enables upcall
    feature on server side and md-cache cache-invalidation on client side.
    There are multiple problems that can arise from this:
    1. The scenario when user wants to, enable upcall for nfs-ganesha setup,
       but do not want to enable md-cache cache-invalidation, as the
       nfs-clients have already cached the metadata and upcall is used to
       to invalidate the nfs-client cache. In this case, users should have
       a way of disabling md-cache invalidation without disabling upcall.

    2. Upcall requires a op-version of GD_OP_VERSION_3_7_0, where as
       md-cache invalidation requires an op version of GD_OP_VERSION_3_9_0.
       Consider a setup where the servers are in op-version
GD_OP_VERSION_3_7_0,
       and th clients are in op-version GD_OP_VERSION_3_9_0. if there is one
       single volume set option, user can enable this feature in this setup.
       But it can lead to stale xattr cache as the xattr invalidation was
       introduced in upcall only in release 3.8. Hence, we should not be
       able to enable md-cache invalidation, if all the servers and clients
       are not on opversion >= GD_OP_VERSION_3_9_0.

    To solve the above mentioned issues, we have seperate volume options
    for enabling md-cache invalidation and upcall. But this can lead to
    issues when user enable md-cache invalidation and forgets to enable
    upcall. Probably in the next release, these can be enables by default.

    Change-Id: Ie70eff97fe12fcb623eec8f4f5861ac065bf483e
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid at redhat.com>
    Reviewed-on: http://review.gluster.org/15314
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: soumya k <skoduri at redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=R8uhxvaJ1S&a=cc_unsubscribe