GlusterFS : Dispersed Configuration2023/06/19 |
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 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/dispersed |
[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: 312f36f7-47a4-48fa-91fc-1e3f8cd3d88f State: Peer in Cluster (Connected) Hostname: node03 Uuid: 299ee00a-9492-4dd3-afab-9df9d3c41960 State: Peer in Cluster (Connected) Hostname: node04 Uuid: 77698649-65bc-4ea5-8072-12a01de51d18 State: Peer in Cluster (Connected) Hostname: node05 Uuid: 4a4d1f71-70ee-47f5-8125-a66318675d37 State: Peer in Cluster (Connected) Hostname: node06 Uuid: 2fe0bcbb-e721-4e0c-9fca-d782ada598c2 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 # confirm volume info root@node01:~# gluster volume info Volume Name: vol_dispersed Type: Disperse Volume ID: 26fef6fc-8cc0-4b02-8c03-31e284673758 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: storage.fips-mode-rchecksum: on transport.address-family: inet nfs.disable: on |
[4] |
Sponsored Link |