Bug 1691616

Summary:	client log flooding with intentional socket shutdown message when a brick is down
Product:	[Community] GlusterFS	Reporter:	Raghavendra G <rgowdapp>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, mchangir, pasik
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:	1679904
Clones:	1695416 (view as bug list)		Environment:
Last Closed:	2019-04-03 04:13:29 UTC	Type:	---
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:	1679904
Bug Blocks:	1672818, 1691620, 1695416, 1732875

Description Raghavendra G 2019-03-22 05:09:53 UTC

+++ This bug was initially created as a clone of Bug #1679904 +++

Description of problem:

client log flooding with intentional socket shutdown message when a brick is down

[2019-02-22 08:24:42.472457] I [socket.c:811:__socket_shutdown] 0-test-vol-client-0: intentional socket shutdown(5)

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

How reproducible:
Always

Steps to Reproduce:
1. 1 X 3 volume created and started over a 3 node cluster
2. mount a fuse client
3. kill a brick
4. Observe that fuse client log is flooded with the intentional socket shutdown message after every 3 seconds.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-03-22 05:14:20 UTC

REVIEW: https://review.gluster.org/22395 (transport/socket: move shutdown msg to DEBUG loglevel) posted (#1) for review on master by Raghavendra G

Comment 2 Worker Ant 2019-04-03 04:13:29 UTC

REVIEW: https://review.gluster.org/22395 (transport/socket: log shutdown msg occasionally) merged (#5) on master by Raghavendra G