ClusterStorage-12-已分层存储的扩展

0.实验前的环境检查与配置

[student@workstation ~]$ lab extend-tier setup
 

1.存储信息

gluster volume info prod-vol查看存储信息。注意:此时已经进行分层。

[root@servera ~]# gluster volume info prod-vol
 
Volume Name: prod-vol
Type: Tier
Volume ID: 3ef06fa0-87b4-4a54-ae03-fd6ee473bbe4
Status: Started
Number of Bricks: 4
Transport-type: tcp
Hot Tier :
Hot Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick1: serverb:/bricks/brick-b2/brick
Brick2: servera:/bricks/brick-a2/brick
Cold Tier:
Cold Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick3: servera:/bricks/brick-a1/brick
Brick4: serverb:/bricks/brick-b1/brick
Options Reconfigured:
cluster.tier-mode: cache
features.ctr-enabled: on
performance.readdir-ahead: on
 

2.重置存储条

gluster volume tier prod-vol detach start启动调整。gluster volume tier prod-vol detach status查看状态信息。 gluster volume tier prod-vol detach commit确认调整。rm -rf /bricks/brick-a2/brick删除存储条。mkdir /bricks/brick-a2/brick重新建立存储条。serverb参照servera操作。gluster volume tier prod-vol attach replica 2 servera:/bricks/brick-a2/brick serverb:/bricks/brick-b2/brick servera:/bricks/brick-a3/brick serverb:/bricks/brick-b3/brick重新向存储卷添加存储条。

[root@servera ~]# gluster volume tier prod-vol detach start
volume detach-tier start: success
ID: d7b34e25-24b9-4ce3-a365-a0c4a6ad341b
[root@servera ~]# gluster volume tier prod-vol detach status
                                    Node Rebalanced-files          size       scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------   -----------   -----------   -----------         ------------     --------------
                               localhost                0        0Bytes            20             0             0            completed              29.00
                 serverb.lab.example.com               20       252.3KB            20             0             0            completed              39.00
[root@servera ~]# gluster volume tier prod-vol detach commit
Removing tier can result in data loss. Do you want to Continue? (y/n) y
volume detach-tier commit: success
Check the detached bricks to ensure all files are migrated.
If files with data are found on the brick path, copy them via a gluster mount point before re-purposing the removed brick. 
[root@servera ~]# rm -rf /bricks/brick-a2/brick
[root@servera ~]# mkdir /bricks/brick-a2/brick
[root@serverb ~]# rm -rf /bricks/brick-b2/brick
[root@serverb ~]# mkdir /bricks/brick-b2/brick
[root@servera ~]# gluster volume tier prod-vol attach replica 2 servera:/bricks/brick-a2/brick serverb:/bricks/brick-b2/brick servera:/bricks/brick-a3/brick serverb:/bricks/brick-b3/brick
volume attach-tier: success
Tiering Migration Functionality: prod-vol: success: Attach tier is successful on prod-vol. use tier status to check the status.
ID: 7d77f013-e49d-4040-b82f-b44520e58f8f
 

3.存储信息

gluster volume info prod-vol查看存储卷信息。注意:可以看到只是热区分层发生了调整,变成了分布复制,而冷区分层并没有发生改变。

[root@servera ~]# gluster volume info prod-vol
 
Volume Name: prod-vol
Type: Tier
Volume ID: 3ef06fa0-87b4-4a54-ae03-fd6ee473bbe4
Status: Started
Number of Bricks: 6
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick1: serverb:/bricks/brick-b3/brick
Brick2: servera:/bricks/brick-a3/brick
Brick3: serverb:/bricks/brick-b2/brick
Brick4: servera:/bricks/brick-a2/brick
Cold Tier:
Cold Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick5: servera:/bricks/brick-a1/brick
Brick6: serverb:/bricks/brick-b1/brick
Options Reconfigured:
cluster.tier-mode: cache
features.ctr-enabled: on
performance.readdir-ahead: on
 

4.存储信息

gluster volume info dev-vol查看存储卷信息。注意:此时的热区分层是分布复制式,有4个存储条。

[root@servera ~]# gluster volume info dev-vol
 
Volume Name: dev-vol
Type: Tier
Volume ID: d465cb78-0455-4331-b4c8-4310a61b92b1
Status: Started
Number of Bricks: 6
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick1: serverb:/bricks/brick-b6/brick
Brick2: servera:/bricks/brick-a6/brick
Brick3: serverb:/bricks/brick-b5/brick
Brick4: servera:/bricks/brick-a5/brick
Cold Tier:
Cold Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick5: servera:/bricks/brick-a4/brick
Brick6: serverb:/bricks/brick-b4/brick
Options Reconfigured:
cluster.tier-mode: cache
features.ctr-enabled: on
performance.readdir-ahead: on
 

5.重置存储条

gluster volume tier dev-vol detach start启动存储卷调整。gluster volume tier dev-vol detach status查看状态信息。rm -rf /bricks/brick-a6/brick删除旧的存储条。mkdir /bricks/brick-a6/brick创建新的存储条。serverb参照servera操作。gluster volume tier dev-vol attach replica 2重新添加存储条。

[root@servera ~]# gluster volume tier dev-vol detach start
volume detach-tier start: success
ID: 6546d24f-46ad-4193-a4ee-607595a22a70
[root@servera ~]# gluster volume tier dev-vol detach status
                                    Node Rebalanced-files          size       scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------   -----------   -----------   -----------         ------------     --------------
                               localhost                0        0Bytes             0             0             0            completed               2.00
                 serverb.lab.example.com                0        0Bytes             0             0             0            completed               3.00
[root@servera ~]# gluster volume tier dev-vol detach commit
Removing tier can result in data loss. Do you want to Continue? (y/n) y
volume detach-tier commit: success
Check the detached bricks to ensure all files are migrated.
If files with data are found on the brick path, copy them via a gluster mount point before re-purposing the removed brick. 
[root@servera ~]# rm -rf /bricks/brick-a6/brick
[root@servera ~]# mkdir /bricks/brick-a6/brick
[root@serverb ~]# rm -rf /bricks/brick-b6/brick
[root@serverb ~]# mkdir /bricks/brick-b6/brick
[root@servera ~]# gluster volume tier dev-vol attach replica 2 \
> servera:/bricks/brick-a6/brick \
> serverb:/bricks/brick-b6/brick
volume attach-tier: success
Tiering Migration Functionality: dev-vol: success: Attach tier is successful on dev-vol. use tier status to check the status.
ID: c3ada7d5-2f3f-4e4b-895d-f87e50e6c911
 

6.存储信息

gluster volume info dev-vol查看存储信息。注意:经过调整,此时热区分层已经只有2个存储条,存储模式也变为副本模式。

[root@servera ~]# gluster volume info dev-vol
 
Volume Name: dev-vol
Type: Tier
Volume ID: d465cb78-0455-4331-b4c8-4310a61b92b1
Status: Started
Number of Bricks: 4
Transport-type: tcp
Hot Tier :
Hot Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick1: serverb:/bricks/brick-b6/brick
Brick2: servera:/bricks/brick-a6/brick
Cold Tier:
Cold Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick3: servera:/bricks/brick-a4/brick
Brick4: serverb:/bricks/brick-b4/brick
Options Reconfigured:
cluster.tier-mode: cache
features.ctr-enabled: on
performance.readdir-ahead: on
 

7.任务测评

lab extend-tier grade进行任务测评。主要包括:热区分层是否启用,热区分层的存储条是否配置正确。

[student@workstation ~]$ lab extend-tier grade

Grading the student's work:

Checking hot tier enabled for prod-vol.........................  PASS
Checking hot tier enabled for dev-vol..........................  PASS
Checking hot tier bricks for prod-vol..........................  PASS
Checking hot tier bricks for dev-vol...........................  PASS

Overall lab grade..............................................  PASS
 

猜你喜欢

转载自blog.csdn.net/ligan1115/article/details/86736277
今日推荐