Bug 955546 - TCP connections are stacking on master geo-replication side if the slave rejects the master IP.
Summary: TCP connections are stacking on master geo-replication side if the slave reje...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.3.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-23 09:20 UTC by florian.leduc
Modified: 2014-12-14 19:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-14 19:40:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Number of established connections grew significantly (11.51 KB, image/png)
2013-04-23 09:20 UTC, florian.leduc
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.