CentOS Stream 9
Sponsored Link

GlusterFS 9 : Add Nodes (Bricks)2022/03/30

 
Add Nodes (Bricks) to existing Cluster.
For example, Add a Node [node03] to the existing Cluster like follows.
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#1] |10.0.0.51 | 10.0.0.52| [GlusterFS Server#2] |
|   node01.srv.world   +----------+----------+   node02.srv.world   |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
           ⇑                      |                      ⇑
     file1, file3 ...             |               file2, file4 ...
                                  |
+----------------------+          |
| [GlusterFS Server#3] |10.0.0.53 |
|   node03.srv.world   +----------+
|                      |
+----------------------+

[1]
Install GlusterFS to a New Node, refer to here, and then Create a directory for GlusterFS volume on the same Path with other Nodes.
[2] Add a New Node to existing Cluster on a node. (OK on any existing node)
# probe new node

[root@node01 ~]#
gluster peer probe node03

peer probe: success.
# confirm status

[root@node01 ~]#
gluster peer status

Number of Peers: 2

Hostname: node02
Uuid: b27b63b2-4b52-4de0-9f24-a63d5293187e
State: Peer in Cluster (Connected)

Hostname: node03
Uuid: 55aeca51-4b31-4a33-820e-60b22a2a26a5
State: Peer in Cluster (Connected)

# confirm existing volume

[root@node01 ~]#
gluster volume info


Volume Name: vol_distributed
Type: Distribute
Volume ID: 352e71e5-2057-4db4-9f2a-c232b0d409cb
Status: Started
Snapshot Count: 0
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: node01:/glusterfs/distributed
Brick2: node02:/glusterfs/distributed
Options Reconfigured:
features.inode-quota: off
features.quota: off
storage.fips-mode-rchecksum: on
transport.address-family: inet
nfs.disable: on

# add new node

[root@node01 ~]#
gluster volume add-brick vol_distributed node03:/glusterfs/distributed

volume add-brick: success
# confirm volume info

[root@node01 ~]#
gluster volume info


Volume Name: vol_distributed
Type: Distribute
Volume ID: 352e71e5-2057-4db4-9f2a-c232b0d409cb
Status: Started
Snapshot Count: 0
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: node01:/glusterfs/distributed
Brick2: node02:/glusterfs/distributed
Brick3: node03:/glusterfs/distributed
Options Reconfigured:
features.inode-quota: off
features.quota: off
storage.fips-mode-rchecksum: on
transport.address-family: inet
nfs.disable: on

# after adding new node, run rebalance volume

[root@node01 ~]#
gluster volume rebalance vol_distributed fix-layout start

volume rebalance: vol_distributed: success: Rebalance on vol_distributed has been started successfully. Use rebalance status command to check status of the rebalance process.
ID: 9df2e4a6-ff36-41e5-b44d-1e8749a692a6

# OK if [Status] turns to [completed]

[root@node01 ~]#
gluster volume status

Status of volume: vol_distributed
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick node01:/glusterfs/distributed         49152     0          Y       2101
Brick node02:/glusterfs/distributed         49152     0          Y       2034
Brick node03:/glusterfs/distributed         49152     0          Y       2025

Task Status of Volume vol_distributed
------------------------------------------------------------------------------
Task                 : Rebalance
ID                   : 9df2e4a6-ff36-41e5-b44d-1e8749a692a6
Status               : completed
Matched Content