[Bugs] [Bug 1453152] [Parallel Readdir] : Mounts fail when performance.parallel-readdir is set to "off"

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17354 committed in release-3.11 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit 42fc1abdb41817b691cda87ddc7ea94129279475
Author: Poornima G <pgurusid at redhat.com>
Date:   Fri May 19 11:09:13 2017 +0530

    rda, glusterd: Change the max of rda-cache-limit to INFINITY

    Issue:
    The max value of rda-cache-limit is 1GB before this patch.
    When parallel-readdir is enabled, there will be many instances of
    readdir-ahead, hence the rda-cache-limit depends on the number of
    instances. Eg: On a volume with distribute count 4, rda-cache-limit
    when parallel-readdir is enabled, will be 4GB instead of 1GB.
    Consider a followinf sequence of operations:
    - Enable parallel readdir
    - Set rda-cache-limit to lets say 3GB
    - Disable parallel-readdir, this results in one instance of readdir-ahead
      and the rda-cache-limit will be back to 1GB, but the current value is 3GB
      and hence the mount will stop working as 3GB > max 1GB.

    Solution:
    To fix this, we can limit the cache to 1GB even when parallel-readdir
    is enabled. But there is no necessity to limit the cache to 1GB, it
    can be increased if the system has enough resources. Hence getting rid
    of the rda-cache-limit max value is more apt. If we just change the
    rda-cache-limit max to INFINITY, we will render older(<3.11) clients
    broken, when the rda-cache-limit is set to > 1GB (as the older clients
    still expect a value < 1GB). To safely change the max value of
    rda-cache-limit to INFINITY, add a check in glusted to verify all
    the clients are > 3.11 if the value exceeds 1GB.

    >Reviewed-on: https://review.gluster.org/17338
    >Smoke: Gluster Build System <jenkins at build.gluster.org>
    >Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    >(cherry picked from commit e43b40296956d132c70ffa3aa07b0078733b39d4)

    Change-Id: Id0cdda3b053287b659c7bf511b13db2e45b92032
    BUG: 1453152
    Signed-off-by: Poornima G <pgurusid at redhat.com>
    Reviewed-on: https://review.gluster.org/17354
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.