Description of problem: Excessive logging in Debug Mode for mem_get. Version-Release number of selected component (if applicable): How reproducible: For debug log level, excessive logging is taking place by mem_get function. Steps to Reproduce: 1. Create dis-rep volume. 2. Perform file operations. 3. Actual results: mem_get is doing excessive logging. Expected results: It should avoid excessive logging. Additional info:
REVIEW: http://review.gluster.org/5086 (loggig: Fix to avoid excessive logging.) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/5086 (logging: Fix to avoid excessive logging.) posted (#2) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/5086 (logging: Fix to avoid excessive logging.) posted (#3) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/5086 (logging: Fix to avoid excessive logging.) posted (#4) for review on master by venkatesh somyajulu (vsomyaju)
COMMIT: http://review.gluster.org/5086 committed in master by Vijay Bellur (vbellur) ------ commit 84e966cc8b6ae06699f8a57bc33d509b30ff777b Author: Venkatesh Somyajulu <vsomyaju> Date: Fri May 24 12:57:19 2013 +0530 logging: Fix to avoid excessive logging. mem_get function: Log message related to mem_pool calloc is removed as its been calculated in mempool 'stats'. This messgae is consuming nearly half of the total log messages in DEBUG mode. dht_hash_compute function: Changed log level from DEBUG to TRACE. client_fdctx_destroy function: Changed log level from DEBUG to TRACE. Change-Id: Ic948db0419e76df4e95ebd0cabaf66eadbaada6b BUG: 966851 Signed-off-by: Venkatesh Somyajulu <vsomyaju> Reviewed-on: http://review.gluster.org/5086 Reviewed-by: Amar Tumballi <amarts> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>