Bug 1714098

Summary:	Make debugging hung frames easier
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1716760 (view as bug list)		Environment:
Last Closed:	2019-05-30 15:55:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1716760

Description Pranith Kumar K 2019-05-27 06:24:20 UTC

Description of problem:

At the moment new stack doesn't populate frame->root->unique in all cases. This makes it difficult to debug hung frames by examining successive state dumps. Fuse and server xlator populate it whenever they can, but other xlators won't be able to assign one when they need to create a new frame/stack. What we need is for unique to be correct. If a stack with same unique is present in successive statedumps, that means the same operation is still in progress. This makes finding hung frames part of debugging hung frames easier.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-05-27 06:27:36 UTC

REVIEW: https://review.gluster.org/22773 (stack: Make sure to have unique call-stacks in all cases) posted (#1) for review on master by Pranith Kumar Karampuri

Comment 2 Worker Ant 2019-05-30 15:55:06 UTC

REVIEW: https://review.gluster.org/22773 (stack: Make sure to have unique call-stacks in all cases) merged (#4) on master by Amar Tumballi