Ubuntu 22.04
Sponsored Link

GlusterFS : Distributed + Replication
2022/08/31
 
Configure Storage Clustering with GlusterFS.
For example, Create a Distributed + Replication volume with 6 Nodes.
Also Configure Arbiter Volume in order to avoid Split Brain.
                                  |
+----------------------+          |          +----------------------+
| [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   |
|                      |                     |                      |
+----------------------+                     +----------------------+
           ⇑                                             ⇑
     file1, file3 ...                             file2, file4 ...

 
It is strongly recommended to use partitions for GlusterFS volumes that are different from the / partition.
On this example, it shows settings on the environment that all nodes has [sdb1] and mount it to [/glusterfs].
[1]
[2] Create a Directory for GlusterFS Volume on all Nodes.
root@node01:~#
mkdir -p /glusterfs/dist-replica

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

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.
# confirm status

root@node01:~#
gluster peer status

Number of Peers: 5

Hostname: node02
Uuid: 43d3d5c3-d801-47f8-b26c-6b7cf6d50094
State: Peer in Cluster (Connected)

Hostname: node03
Uuid: 270b4d81-0a18-4e20-b913-b8dbf8d6fe0b
State: Peer in Cluster (Connected)

Hostname: node04
Uuid: 0b917019-22c2-4132-b83a-378bed783a32
State: Peer in Cluster (Connected)

Hostname: node05
Uuid: edd4cfc0-0ffc-4074-8923-94123995bbd8
State: Peer in Cluster (Connected)

Hostname: node06
Uuid: 55511023-9e47-4086-9958-d73108c2b7c0
State: Peer in Cluster (Connected)

# create volume

root@node01:~#
gluster volume create vol_dist-replica replica 3 arbiter 1 transport tcp \
node01:/glusterfs/dist-replica \
node02:/glusterfs/dist-replica \
node03:/glusterfs/dist-replica \
node04:/glusterfs/dist-replica \
node05:/glusterfs/dist-replica \
node06:/glusterfs/dist-replica

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

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

volume start: vol_dist-replica: success
# confirm volume info

root@node01:~#
gluster volume info


Volume Name: vol_dist-replica
Type: Distributed-Replicate
Volume ID: 8041114d-1b2b-4e86-9ca6-7ac34d4f2a05
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x (2 + 1) = 6
Transport-type: tcp
Bricks:
Brick1: node01:/glusterfs/dist-replica
Brick2: node02:/glusterfs/dist-replica
Brick3: node03:/glusterfs/dist-replica (arbiter)
Brick4: node04:/glusterfs/dist-replica
Brick5: node05:/glusterfs/dist-replica
Brick6: node06:/glusterfs/dist-replica (arbiter)
Options Reconfigured:
cluster.granular-entry-heal: on
storage.fips-mode-rchecksum: on
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off
[4]
Matched Content