8.8. Creating Distributed Striped Volumes


Distributed-Striped volume is a technology preview feature. Technology Preview features are not fully supported under Red Hat subscription level agreements (SLAs), may not be functionally complete, and are not intended for production use. However, these features provide early access to upcoming product innovations, enabling customers to test functionality and provide feedback during the development process.
Distributed striped volumes stripes files across two or more nodes in the trusted storage pool. For best results, you should use distributed striped volumes if the requirement is to scale storage and in high concurrency environments where accessing very large files is critical.


The number of bricks should be a multiple of the stripe count for a distributed striped volume.
Illustration of a Distributed Striped Volume

Figure 8.6. Illustration of a Distributed Striped Volume

To create a distributed striped volume
  1. Create a trusted storage pool as described earlier in Section 7.1, “Adding Servers to Trusted Storage Pool”.
  2. Create the distributed striped volume:
    # gluster volume create NEW-VOLNAME [stripe COUNT] [transport tcp | rdma | tcp,rdma] NEW-BRICK...
    For example, to create a distributed striped volume across four storage servers:
    # gluster volume create test-volume stripe 2 transport tcp server1:/exp1 server1:/exp2 server2:/exp3 server2:/exp4
    Creation of test-volume has been successful
    Please start the volume to access data.
    If the transport type is not specified, tcp is used as the default. You can also set additional options if required, such as auth.allow or auth.reject. For more information, see Section 10.1, “Tuning Volume Options”


    Make sure you start your volumes before you try to mount them or else client operations after the mount will hang, see Section 8.10, “Starting Volumes ” for details.