Bug 764441 (GLUSTER-2709)

Summary:	issues with port (re-)configuration in client protocol
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <amarts>
Component:	transport	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, rfortier, vraman
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:37:58 UTC	Type:	---
Regression:	RTP	Mount Type:	---
Documentation:	DNR	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.