| Summary: | can't add tcp transport type to already existing volume with rdma transport | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | csb sysadmin <admin> |
| Component: | glusterd | Assignee: | Krutika Dhananjay <kdhananj> |
| Status: | CLOSED WONTFIX | QA Contact: | Sudhir D <sdharane> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.0 | CC: | amarts, gluster-bugs, sdharane, shaines, surs, vagarwal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.4.0.33rhs-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-03 09:26:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
csb sysadmin
2012-02-24 01:37:52 UTC
This is not supported with current versions. Will consider it as a feature request, as there exists a workaround 1) delete your rdma volume 2) create the volume with same bricks with both 'tcp,rdma' transport If I delete the volume, I don't think gluster currently allows a re-create if the bricks have existing data in them right? Which brings up another feature request to have an option to force this if required. The workaround I used was to : 1) Create a test stripe volume that basically has the same setup except it has rdma,tcp 2) Turn glusterd and glusterfsd off 3) Add transport-type tcp,rdma to all the server .vol files 4) Create a <volname>.rdma-fuse.vol file in addition to the <volname>-fuse.vol similar to the test volume 5) In the info file, change transport-type to 2 6) Turn glusterd and glusterfsd on @csb sysadmin, the bricks which were part of any volume have trusted.glusterfs.volume-id set to the volume-id as seen in 'gluster volume info'. This is not removed by glusterd on delete volume, to serve as a reminder to the administrator who can accidentally add the brick (which may still have old data, along with gfid from past life.) to a newly created volume. We expect the administrator to perform 'cleaning' of bricks using extras/clear_xattrs.sh (or any custom-made script), before the brick is made a part of any volume. As for the problem of not being able to change transport-type, I haven't managed to look into it yet. Will look into it and get back to you as early as possible. http://review.gluster.org/4008 merged upstream... Moving out of Big Bend since RDMA support is not available in Big Bend,2.1 Moving out of Big Bend since RDMA support is not available in Big Bend,2.1 Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request. |