glusterd process consumes lots of memory which causes the node to trigger OOM

Issue

• The glusterfsd process is consuming lots of memory and causing the system to trigger OOM

• glusterd process consumes lots of memory which causes the node to trigger OOM

• What does "Locking failed on x.x.x.. Please check log file for details" in gluster logs indicate ?

~ Snippet from the gluster logs:

[2015-02-27 11:43:23.429066] E [glusterd-utils.c:156:glusterd_lock] 0-management: Unable to get lock for uuid: cc22785c-d965-4058-be63-1bb851cddf3e, lock held by: 5cb670d0-081b-4dae-9c25-7ec2550863aa
[2015-02-27 11:43:23.437740] E [glusterd-utils.c:156:glusterd_lock] 0-management: Unable to get lock for uuid: cc22785c-d965-4058-be63-1bb851cddf3e, lock held by: 5cb670d0-081b-4dae-9c25-7ec2550863aa
[2015-02-27 11:43:23.450208] E [glusterd-utils.c:156:glusterd_lock] 0-management: Unable to get lock for uuid: cc22785c-d965-4058-be63-1bb851cddf3e, lock held by: 5cb670d0-081b-4dae-9c25-7ec2550863aa

[2015-02-27 12:07:22.913102] E [glusterd-op-sm.c:3054:glusterd_op_ac_lock] 0-management: Unable to acquire lock for testvol
[2015-02-27 12:07:22.913148] E [glusterd-op-sm.c:6581:glusterd_op_sm] 0-management: handler returned: -1
[2015-02-27 12:07:22.914443] W [glusterd-locks.c:641:glusterd_mgmt_v3_unlock] 0-management: Lock owner mismatch. Lock for vol testvol held by 5cb670d0-081b-4dae-9c25-7ec2550863aa

[2015-02-27 12:18:53.762199] E [glusterd-syncop.c:85:gd_mgmt_v3_collate_errors] 0-: Locking failed on x.x.x.. Please check log file for details.
[2015-02-27 12:18:53.762314] E [glusterd-syncop.c:1654:gd_sync_task_begin] 0-management: Locking Peers Failed.
[2015-02-27 12:18:53.763479] E [glusterd-syncop.c:85:gd_mgmt_v3_collate_errors] 0-: Unlocking failed on x.x.x.x. Please check log file for details.