[Bugs] [Bug 1201203] glusterd OOM killed, when repeating volume set operation in a loop

bugzilla at redhat.com bugzilla at redhat.com
Mon Mar 30 12:40:23 UTC 2015


--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9862 committed in master by Kaleb KEITHLEY
(kkeithle at redhat.com) 
commit 4481b03ae2e8ebbd091b0436b96e97707b4ec41f
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Mar 12 15:43:56 2015 +0530

    core : free up mem_acct.rec in xlator_destroy

    We've observed that glusterd was OOM killed after some minutes when volume
    command was run in a loop.


    Initially the suspection was in glusterd code, but a deep dive into the
    revealed that while validating all the options as part of graph
    at the time of freeing up the xlator object its one of the member mem_acct
    left over which causes memory leak.


    Free up xlator's mem_acct.rec in xlator_destroy ()

    Change-Id: Ie9e7267e1ac4ab7b8af6e4d7c6660dfe99b4d641
    BUG: 1201203
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/9862
    Reviewed-by: Niels de Vos <ndevos at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle 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=XgVnboS5KT&a=cc_unsubscribe

More information about the Bugs mailing list