GlusterFS 11 : Replication Configuration2025/05/13

Configure Storage Clustering with GlusterFS.

For example, Create a Replication volume with 3 Nodes.

It's possible to create Replication volume with 2 Nodes but it's not recommended because split-brain syndrome maybe happens on [replica 2 volume].
As a countermeasure for split-brain, it is recommended to create volume with more than 3 Nodes or set [arbiter volume].

                                  |
+----------------------+          |          +----------------------+
| [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 |
|   node03.srv.world   +----------+
|                      |
+----------------------+

	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]	Install GlusterFS Server on All Nodes, refer to here.
[2]	Create a Directory for GlusterFS Volume on all Nodes.

[root@node01 ~]#

mkdir -p /glusterfs/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.

# confirm status

[root@node01 ~]#

gluster peer status

Number of Peers: 2

Hostname: node02
Uuid: 007efbd1-d654-464f-95e3-cf9398bc0c2e
State: Peer in Cluster (Connected)

Hostname: node03
Uuid: 6c82e4c7-53bf-4d6e-b641-5578936b048f
State: Peer in Cluster (Connected)

# create volume

[root@node01 ~]#

gluster volume create vol_replica replica 3 transport tcp \
node01:/glusterfs/replica \
node02:/glusterfs/replica \
node03:/glusterfs/replica

volume create: vol_replica: success: please start the volume to access data

# start volume

[root@node01 ~]#

gluster volume start vol_replica

volume start: vol_replica: success

# confirm volume info

[root@node01 ~]#

gluster volume info


Volume Name: vol_replica
Type: Replicate
Volume ID: 416a2361-0ba9-4d29-a946-a8a55e5e369a
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: node01:/glusterfs/replica
Brick2: node02:/glusterfs/replica
Brick3: node03:/glusterfs/replica
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]	To mount GlusterFS volume on Client Hosts, refer to here.

Matched Content