Debian 9 Stretch
Sponsored Link

GlusterFS : Striping + Replication Setting
2017/06/21
 
Configure Storage Clustering.
For example, create a Striping + Replication volume with 4 servers.
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#1] |10.0.0.51 | 10.0.0.52| [GlusterFS Server#2] |
|   node01.srv.world   +----------+----------+   node02.srv.world   |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#3] |10.0.0.53 | 10.0.0.54| [GlusterFS Server#4] |
|   node03.srv.world   +----------+----------+   node04.srv.world   |
|                      |                     |                      |
+----------------------+                     +----------------------+

 
It is recommended to use partitions for GlusterFS volumes which are different from the / partition. The environment on this example is set as that sdb1 is mounted on [/var/lib/glusterfs] directory for GlusterFS Configuration on all Nodes.
[1]
[2] Create a Directory for GlusterFS Volume on all Nodes.
root@node01:~#
mkdir -p /var/lib/glusterfs/strip-replica

[3] Configure Clustering like follows on a node. (it's OK on any node)
# probe the node

root@node01:~#
gluster peer probe node02

peer probe: success.
root@node01:~#
gluster peer probe node03

peer probe: success.
root@node01:~#
gluster peer probe node04

peer probe: success.
# show status

root@node01:~#
gluster peer status

Number of Peers: 3

Hostname: node02
Uuid: a39156f3-32cb-451e-9e34-08ce504d72bb
State: Peer in Cluster (Connected)

Hostname: node03
Uuid: b86b98e4-12b6-4581-984d-da420d7b3bbe
State: Peer in Cluster (Connected)

Hostname: node04
Uuid: 6a1fb91a-f483-48c7-8dc7-0f2ac4d8db94
State: Peer in Cluster (Connected)

# create volume

root@node01:~#
gluster volume create vol_strip-replica stripe 2 replica 2 transport tcp \
node01:/var/lib/glusterfs/strip-replica \
node02:/var/lib/glusterfs/strip-replica \
node03:/var/lib/glusterfs/strip-replica \
node04:/var/lib/glusterfs/strip-replica

volume create: vol_strip-replica: success: please start the volume to access data
# start volume

root@node01:~#
gluster volume start vol_strip-replica

volume start: vol_strip-replica: success
# show volume info

root@node01:~#
gluster volume info


Volume Name: vol_strip-replica
Type: Striped-Replicate
Volume ID: 67bf7ce3-d990-48c6-8998-47ce7f032209
Status: Created
Snapshot Count: 0
Number of Bricks: 1 x 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: node01:/var/lib/glusterfs/strip-replica
Brick2: node02:/var/lib/glusterfs/strip-replica
Brick3: node03:/var/lib/glusterfs/strip-replica
Brick4: node04:/var/lib/glusterfs/strip-replica
Options Reconfigured:
transport.address-family: inet
performance.readdir-ahead: on
nfs.disable: on
[4] If use NFS mount from Clients, Start required services first and also configure like follwos.
root@node01:~#
gluster volume set vol_strip-replica nfs.disable off

volume set: success
[5]
Matched Content
 
Tweet