[Bugs] [Bug 1417028] option performance.parallel-readdir can cause OOM in large volumes

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16459 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit 6ebbfb67315ae9abc4058775d3b48d5abfe306d5
Author: Poornima G <pgurusid at redhat.com>
Date:   Tue Jan 17 17:45:59 2017 +0530

    glusterd, rda: If parallel readdir is enabled, split the cache limit

    With patch http://review.gluster.org/#/c/16072/ readdir-ahead can be
    loaded as a child of dht. i.e. there can be more than one instance
    of readdir-ahead in client process. In this case the rda-cache-size
    should be split among all the readdir-ahead instances. Also the
    value of rda-request-size is considered as the minimum cache size
    of any readdir-ahead instance.

    >Change-Id: Iea2fe6d4c46adc09dd2e9a252332a0fe3005f2b9
    >BUG: 1401812
    >Signed-off-by: Poornima G <pgurusid at redhat.com>
    >Reviewed-on: https://review.gluster.org/16424
    >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: Kaushal M <kaushal at redhat.com>
    >Reviewed-by: Raghavendra G <rgowdapp at redhat.com>

    Change-Id: Iea2fe6d4c46adc09dd2e9a252332a0fe3005f2b9
    BUG: 1417028
    Signed-off-by: Poornima G <pgurusid at redhat.com>
    (cherry picked from commit f245dc568e3c22882e22ddd3e26a4207f5704e3b)
    Reviewed-on: https://review.gluster.org/16459
    Tested-by: Raghavendra G <rgowdapp at redhat.com>
    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: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    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.