Description of problem: Currently we log the tuple (server-xlator-name, callid) for identifying a call in log messages. However it does not uniquely identify the operation when there are multiple clients (since operations from all clients go through same server). Adding connection-id resolves this ambiguity. Also printing connection-id helps diagnoise failures associated with connection state (like fds, locks). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/5011 (protocol/server: print connection-id in fop failure logs.) posted (#3) for review on master by Raghavendra G (raghavendra)
REVIEW: http://review.gluster.org/5011 (protocol/server: print connection-id in fop failure logs.) posted (#4) for review on master by Raghavendra G (raghavendra)
REVIEW: http://review.gluster.org/5147 (just a test Signed-off-by: jian.hou <hjimmy19870806>) posted (#1) for review on release-3.4 by 健 侯 (hjimmy19870806)
REVIEW: http://review.gluster.org/5147 (just a test) posted (#2) for review on release-3.4 by 健 侯 (hjimmy19870806)
COMMIT: http://review.gluster.org/5011 committed in master by Vijay Bellur (vbellur) ------ commit 1d6f6a65d76f0e8dc9b62fdae305b6246ce268c5 Author: Raghavendra G <raghavendra> Date: Wed May 15 15:54:29 2013 +0530 protocol/server: print connection-id in fop failure logs. Currently we have tuple (server-xlator-name, callid) for identifying a call. However it does not uniquely identify the operation when there are multiple clients (since operations from all clients go through same server). Adding connection-id resolves this ambiguity. Also printing connection-id helps diagnose failures associated with connection state (like fds, locks). Change-Id: I13563bd06ee9b72fc1a10d239f77db5183658573 BUG: 963540 Signed-off-by: Raghavendra G <raghavendra> Reviewed-on: http://review.gluster.org/5011 Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com>