Bug 1642854

Summary:	glusterd: raise default transport.listen-backlog to 1024
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Milind Changire <mchangir>
Component:	glusterd	Assignee:	Milind Changire <mchangir>
Status:	CLOSED ERRATA	QA Contact:	Rochelle <rallan>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.4	CC:	amukherj, bugs, mchangir, rhs-bugs, sanandpa, sankarshan, sheggodu, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.z Batch Update 2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-27	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1642850	Environment:
Last Closed:	2018-12-17 17:07:11 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:	1642850
Bug Blocks:

Description Milind Changire 2018-10-25 08:38:17 UTC

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

Description of problem:
data center setups with large number of bricks with replication causes a flood of connections to glusterd causing connections to be dropped due to insufficient backlog queue length

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


How reproducible:
frequently

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
connections to glusterd should not be dropped or refused

Additional info:

Comment 2 Atin Mukherjee 2018-10-25 08:49:48 UTC

This was seen in ENEL setup.

Comment 3 Milind Changire 2018-10-25 09:05:34 UTC

upstream patch: https://review.gluster.org/c/glusterfs/+/21482

Comment 12 errata-xmlrpc 2018-12-17 17:07:11 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, 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-2018:3827