GlusterFS 8 : Dispersed Configuration2020/09/24 |
|
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 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. # confirm status [root@node01 ~]# gluster peer status Number of Peers: 5 Hostname: node02 Uuid: 4617abc0-ed4a-48e0-ae26-b06ae6da8391 State: Peer in Cluster (Connected) Hostname: node03 Uuid: 1b231014-5e7a-4c25-a209-0c430df04635 State: Peer in Cluster (Connected) Hostname: node04 Uuid: 294f517e-e752-4bfa-a687-0a90e8c2f730 State: Peer in Cluster (Connected) Hostname: node05 Uuid: 7a84cd93-6adb-4e12-87e2-1a9052f99d5c State: Peer in Cluster (Connected) Hostname: node06 Uuid: 95134a30-5034-4197-923a-c6bf0f530608 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: dd2c7e3f-b361-4e25-9753-4a902956f61a 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 |