diff options
| author | Raghavendra G <raghavendra@gluster.com> | 2013-05-15 15:54:29 +0530 |
|---|---|---|
| committer | Vijay Bellur <vbellur@redhat.com> | 2013-06-18 23:27:20 -0700 |
| commit | 1d6f6a65d76f0e8dc9b62fdae305b6246ce268c5 (patch) | |
| tree | 7282967fb32a2f417ed93c852832fd49a7c314d1 /xlators/nfs/server/src/nfs3.c | |
| parent | 78a2e27ec7d85ed5e915817c9bcc080919791b7b (diff) | |
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@gluster.com>
Reviewed-on: http://review.gluster.org/5011
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Diffstat (limited to 'xlators/nfs/server/src/nfs3.c')
0 files changed, 0 insertions, 0 deletions