Bug 1575887

Summary:	Additional log messages in dht_readdir(p)_cbk
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1579736 (view as bug list)		Environment:
Last Closed:	2018-10-23 15:07:59 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:	1579736

Description Nithya Balachandran 2018-05-08 07:53:28 UTC

Description of problem:

We have seen issues recently where files/directories do not show up on the mountpoint though they exist on the bricks. As DHT filters out entries returned by the bricks, it is useful to know what entries have reached DHT and which ones have been filtered out in order to debug such issues.

Adding debug messages to dht_readdir(p)_cbk will allow us to see this at the DHT layer.


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 2018-05-08 08:29:49 UTC

REVIEW: https://review.gluster.org/19980 (cluster/dht: Debug logs in dht_readdir(p)_cbk) posted (#1) for review on master by N Balachandran

Comment 2 Worker Ant 2018-05-09 03:45:58 UTC

COMMIT: https://review.gluster.org/19980 committed in master by "Raghavendra G" <rgowdapp> with a commit message- cluster/dht: Debug logs in dht_readdir(p)_cbk

Additional log messages to help debug issues
with file listings.

Change-Id: Iccd07498ba01d597c0c40f026f4177dd06d7e901
fixes: bz#1575887
Signed-off-by: N Balachandran <nbalacha>

Comment 3 Shyamsundar 2018-10-23 15:07:59 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/