Bug 764441 (GLUSTER-2709) - issues with port (re-)configuration in client protocol
Summary: issues with port (re-)configuration in client protocol
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2709
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 06:55 UTC by Amar Tumballi
Modified: 2013-12-19 00:06 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:37:58 UTC
Regression: RTP
Mount Type: ---
Documentation: DNR
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amar Tumballi 2011-04-11 06:55:29 UTC 
If the brick goes down and comes up in different port, then client-protocol is not getting reconnected to the new process at all, instead keeps trying to reconnect on the old port.
Comment 1 Anand Avati 2011-05-30 06:08:03 UTC 
PATCH: http://patches.gluster.com/patch/6841 in master (rpc-clnt: consider the (re-)configured port for only one connect() call)
Comment 2 Rahul C S 2011-09-20 09:03:10 UTC 
Transport end-point not connected error still happening on master.
Comment 3 Amar Tumballi 2012-10-19 05:06:39 UTC 
should be fixed with http://review.gluster.org/4044. marking it as closed.
Note You need to log in before you can comment on or make changes to this bug.