Bug 976574

Summary:	Feature request for transport tcp/rdma
Product:	[Community] GlusterFS	Reporter:	Bryan Whitehead <bwhitehead>
Component:	cli	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-22 15:46:38 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:

Description Bryan Whitehead 2013-06-20 20:46:53 UTC

Description of problem:
starting with version 3.4.x of gluster, the RDMA code has undergone a pretty good rewrite - making RDMA worth directly using. Unfortunately, due to RDMA not being stable/reliable in previous version, many installs of gluster are using IPoIB and therefore only tcp as the transport.

Looking to have something along the lines like this:
gluster volume BLAH set transport tcp,rdma

after this propagates, fuse mounts would remount automatically to use rdma or a "mount.glusterfs -o remount,transport=rdma /mount/path" should work.

Version-Release number of selected component (if applicable):
hopefully some release of 3.4.x would get this feature so RDMA installs can go native.

How reproducible:
this feature doesn't exist yet.

Steps to Reproduce:
1. cannot

Actual results:
sad realization you're stuck with IPoIB

Expected results:
Switching to IPoIB to native rdma is a simple process.

Additional info:
i like turtles

Comment 1 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC

because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.