Debian 10 Buster
Sponsored Link

GlusterFS : Dispersed Configuration2019/07/17

 
Configure Storage Clustering with GlusterFS.
For example, create a Dispersed volume with 6 Nodes.
Dispersed Volumes is based on Erasure Coding (EC).
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#1] |10.0.0.51 | 10.0.0.54| [GlusterFS Server#4] |
|   node01.srv.world   +----------+----------+   node04.srv.world   |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#2] |10.0.0.52 | 10.0.0.55| [GlusterFS Server#5] |
|   node02.srv.world   +----------+----------+   node05.srv.world   |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#3] |10.0.0.53 | 10.0.0.56| [GlusterFS Server#6] |
|   node03.srv.world   +----------+----------+   node06.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 [/glusterfs] directory for GlusterFS Configuration on all Nodes.
[1]
[2] Create a Directory for GlusterFS Volume on all Nodes.
root@node01:~#
mkdir -p /glusterfs/dispersed

[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.
root@node01:~#
gluster peer probe node05

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

peer probe: success.
# show status

root@node01:~#
gluster peer status

Number of Peers: 5

Hostname: node02
Uuid: 5cbde6d6-0a59-4511-a0e0-88609f6444ec
State: Peer in Cluster (Connected)

Hostname: node03
Uuid: f248cfa3-28cc-41b0-ab6f-135ca74b278c
State: Peer in Cluster (Connected)

Hostname: node04
Uuid: 3964d9df-6839-4eb5-8c6d-0f34cd604018
State: Peer in Cluster (Connected)

Hostname: node05
Uuid: d914c95b-756c-47da-9357-d1bff882e388
State: Peer in Cluster (Connected)

Hostname: node06
Uuid: c5ab5d35-0f86-4bf9-aa8e-e490e4c2bbf0
State: Peer in Cluster (Connected)

# create volume

root@node01:~#
gluster volume create vol_dispersed disperse-data 4 redundancy 2 transport tcp \
node01:/glusterfs/dispersed \
node02:/glusterfs/dispersed \
node03:/glusterfs/dispersed \
node04:/glusterfs/dispersed \
node05:/glusterfs/dispersed \
node06:/glusterfs/dispersed

volume create: vol_dispersed: success: please start the volume to access data
# start volume

root@node01:~#
gluster volume start vol_dispersed

volume start: vol_dispersed: success
# show volume info

root@node01:~#
gluster volume info


Volume Name: vol_dispersed
Type: Disperse
Volume ID: a0fe45e0-95e0-4d74-a117-a61f4166efef
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (4 + 2) = 6
Transport-type: tcp
Bricks:
Brick1: node01:/glusterfs/dispersed
Brick2: node02:/glusterfs/dispersed
Brick3: node03:/glusterfs/dispersed
Brick4: node04:/glusterfs/dispersed
Brick5: node05:/glusterfs/dispersed
Brick6: node06:/glusterfs/dispersed
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
[4]
Matched Content