Bug 955546

Summary: TCP connections are stacking on master geo-replication side if the slave rejects the master IP.
Product: [Community] GlusterFS Reporter: florian.leduc
Component: geo-replicationAssignee: Csaba Henk <csaba>
Status: CLOSED DEFERRED QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 3.3.1CC: bugs, gluster-bugs, rwheeler, vshankar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-14 19:40:30 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:
Attachments:
Description Flags
Number of established connections grew significantly none

Description florian.leduc 2013-04-23 09:20:48 UTC
Created attachment 738895 [details]
Number of established connections grew significantly

Description of problem:

If you rejects the master IP on the geo-replication slave (via glusterFS client, not SSH) , TCP connections just keep stacking on the master.

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


How reproducible:

Often

Steps to Reproduce:
1. Set 1 volume geo-replicated to a slave
2. Reject the master IP on the slave volume
3. netstat -laptue |grep gluster | wc -l 
  
Actual results:

The number of connections should grow infinitely.

Expected results:

Connection should be closed after some time. 

Additional info:

Comment 1 Niels de Vos 2014-11-27 14:54:21 UTC
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.