summaryrefslogtreecommitdiffstats
path: root/xlators/features
diff options
context:
space:
mode:
authorAtin Mukherjee <amukherj@redhat.com>2015-03-12 15:43:56 +0530
committerKaleb KEITHLEY <kkeithle@redhat.com>2015-03-30 05:40:19 -0700
commit4481b03ae2e8ebbd091b0436b96e97707b4ec41f (patch)
tree1ae9e1776b91737a3e8ed13cad639eb777ac8125 /xlators/features
parentd2629aef8302c6b7d832063351c0ce1f2f2efbdd (diff)
core : free up mem_acct.rec in xlator_destroy
Problem: We've observed that glusterd was OOM killed after some minutes when volume set command was run in a loop. Analysis: Initially the suspection was in glusterd code, but a deep dive into the codebase revealed that while validating all the options as part of graph reconfiguration at the time of freeing up the xlator object its one of the member mem_acct is left over which causes memory leak. Solution: Free up xlator's mem_acct.rec in xlator_destroy () Change-Id: Ie9e7267e1ac4ab7b8af6e4d7c6660dfe99b4d641 BUG: 1201203 Signed-off-by: Atin Mukherjee <amukherj@redhat.com> Reviewed-on: http://review.gluster.org/9862 Reviewed-by: Niels de Vos <ndevos@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com> Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com> Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
Diffstat (limited to 'xlators/features')
0 files changed, 0 insertions, 0 deletions