need fixed in version for this, hence reopening the bug. (also this bug is targetted for 2.0.z, need to see if its actually part of 2.1.0).

Verified with the build: glusterfs-3.4.0.44rhs-1.el6rhs.x86_64

Analysed the self heal daemon log after running multiple self heal cases of more than 1L entries. 

# du -sh /var/log/glusterfs/glustershd.log 
42M	/var/log/glusterfs/glustershd.log

# ./log_analyzer.sh /var/log/glusterfs/glustershd.log 
afr_dir_exclusive_crawl:7
afr_find_child_position:3
afr_log_self_heal_completion_status:155083
afr_notify:9
afr_sh_post_nonblocking_entry_cbk:28
client3_3_entrylk_cbk:28
client3_3_inodelk_cbk:28
client_query_portmap_cbk:15
client_rpc_notify:21
client_set_lk_version_cbk:18
client_setvolume_cbk:54
gf_add_cmdline_options:6
main:1
notify:42
rpc_clnt_reconfig:18
select_server_supported_programs:18
socket_connect_finish:6
socket_init:28
__socket_rwv:6
========= Error Functions ========
afr_find_child_position:3
afr_notify:3
afr_sh_post_nonblocking_entry_cbk:28
client3_3_entrylk_cbk:28
client3_3_inodelk_cbk:28
client_query_portmap_cbk:15
socket_connect_finish:6
__socket_rwv:6

Marking it as verified. Will open new bugs when some specific logs are reported in excess.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1769.html