[Bugs] [Bug 1662679] New: Log connection_id in statedump for posix-locks as well for better debugging experience
bugzilla at redhat.com
bugzilla at redhat.com
Mon Dec 31 14:48:26 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1662679
Bug ID: 1662679
Summary: Log connection_id in statedump for posix-locks as well
for better debugging experience
Product: GlusterFS
Version: mainline
Status: NEW
Component: locks
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: kdhananj at redhat.com
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Description of problem:
BEFORE:
posixlk.posixlk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0,
pid = 13635, owner=2dd2c3a11706dc8c, client=0x7f159012b000,
connection-id=(null), granted at 2018-12-31 14:20:42
AFTER:
posixlk.posixlk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0,
pid = 10977, owner=b485e33df21bdaa2, client=0x7fa24c01ab90,
connection-id=CTX_ID:68e12340-eed2-4386-bf5e-1f43cf8693d9-GRAPH_ID:0-
PID:10901-HOST:dhcp35-215.lab.eng.blr.redhat.com-PC_NAME:patchy-client-0-
RECON_NO:-0, granted at 2018-12-31 14:33:50
Printing the connection id helps figure which host the client is running on and
what it's pid is. This information was found to be lacking in one of the bzs
where there was a deadlock in containerized workload due to lock not released
posisbly by heketi and the client could not be easily located due to missing
conn id info.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list