Bug 2015937

Summary:	Introduce retries option to bind a socket for gluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Sayalee <saraut>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rhgs-3.5	CC:	rhs-bugs, sajmoham, saraut, sheggodu, tshacked, vdas
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Batch Update 7
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-62	Doc Type:	No Doc Update
Doc Text:	If this bug requires documentation, please select an appropriate Doc Type value.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-31 12:37:31 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:	2015122

Description Mohit Agrawal 2021-10-20 12:06:32 UTC

Currently gluster processes call bind call only once to bind a socket, If it does not return success the process has exit. Sometime the kernel takes time to cleanup socket fd the situation is normal when a user has started a gluster process again and again usually in case of client process(shd,quota,nfs) happens as graph changes.If socket fd is not cleanup then bind throw an error EAADRINUSE and process exit.In that case a user has to restart the process again and again unless the port is not cleanup, we observed the similar kind of behavior multiple times in downstream on customer environment and for product aspect it does not create good impression.


Solution: To avoid an issue we introduce a retries option(https://bugzilla.redhat.com/show_bug.cgi?id=1743020) long time ago in upstream i think same we need to backport in downstream also.

Comment 1 Mohit Agrawal 2021-10-20 12:09:25 UTC

The retries option is not harmful it does tries to call bind retry(5 to 10 times) to avoid an issue.
The recent downstream bugzilla(https://bugzilla.redhat.com/show_bug.cgi?id=2015122) because of the similar issue.

Comment 19 errata-xmlrpc 2022-05-31 12:37:31 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glusterfs bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4840