Blob Blame History Raw
From ccac7336bb6fa667b4f9b51426440d898ff3d184 Mon Sep 17 00:00:00 2001
From: Milind Changire <mchangir@redhat.com>
Date: Mon, 5 Nov 2018 19:38:08 +0530
Subject: [PATCH 422/444] glusterd: raise default transport.listen-backlog

Problem:
data center setups with large number of bricks with replication
causes a flood of connections from bricks and self-heal daemons
to glusterd causing connections to be dropped due to insufficient
listener socket backlog queue length

Solution:
raise default value of transport.listen-backlog to 1024

mainline:
> Reviewed-on: https://review.gluster.org/c/glusterfs/+/21482
> Change-Id: I879e4161a88f1e30875046dff232499a8e2e6c51
> fixes: bz#1642850
> Signed-off-by: Milind Changire <mchangir@redhat.com>

Change-Id: I879e4161a88f1e30875046dff232499a8e2e6c51
BUG: 1642854
Signed-off-by: Milind Changire <mchangir@redhat.com>
Reviewed-on: https://code.engineering.redhat.com/gerrit/154959
Tested-by: RHGS Build Bot <nigelb@redhat.com>
Reviewed-by: Sunil Kumar Heggodu Gopala Acharya <sheggodu@redhat.com>
---
 libglusterfs/src/glusterfs.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libglusterfs/src/glusterfs.h b/libglusterfs/src/glusterfs.h
index d71a9c1..5e641fd 100644
--- a/libglusterfs/src/glusterfs.h
+++ b/libglusterfs/src/glusterfs.h
@@ -73,7 +73,7 @@
 #endif
 
 #define GLUSTERD_MAX_SNAP_NAME  255
-#define GLUSTERFS_SOCKET_LISTEN_BACKLOG  10
+#define GLUSTERFS_SOCKET_LISTEN_BACKLOG  1024
 #define ZR_MOUNTPOINT_OPT       "mountpoint"
 #define ZR_ATTR_TIMEOUT_OPT     "attribute-timeout"
 #define ZR_ENTRY_TIMEOUT_OPT    "entry-timeout"
-- 
1.8.3.1