Bug 976574 - Feature request for transport tcp/rdma
Feature request for transport tcp/rdma
Status: CLOSED EOL
Product: GlusterFS
Classification: Community
Component: cli (Show other bugs)
mainline
All All
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-20 16:46 EDT by Bryan Whitehead
Modified: 2015-10-22 11:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-22 11:46:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bryan Whitehead 2013-06-20 16:46:53 EDT
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 11:46:38 EDT
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.

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