Example Analysis of ceph pool Management in docker

This article shares with you the content of a sample analysis of ceph pool management in docker. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

You can think of PG as a logical container that contains multiple objects, pool-pg-osd-disk

Recommendation: set 128pg when less than 5 osds

5-10osds, set 512 pg.

10-50 osds, set 1024 pg.

Check out what pool we have:

[root@k8s-node3 ~] # ceph osd pool lsrbd

Check how many pg there are in the pool of rbd:

[root@k8s-node3 ~] # ceph osd pool get rbd pg_numpg_num: 64

Modify the number of pg:

[root@k8s-node3 ~] # ceph osd pool set rbd pg_num 128set pool 0 pg_num to 128

CRUSH maps CRUSH is an important part of allowing Ceph to scale without performance bottlenecks, without scalability constraints, and without a single point of failure. The CRUSH mapping provides the physical topology of the cluster to the CRUSH algorithm to determine where the data of the object and its copies should be stored.

View pool types

[root@k8s-node3 ~] # ceph osd crush rule list ["replicated_ruleset"]

There are two types: and erasure, one is replication, and the other is erase pool.

[root@k8s-node3 ~] # ceph osd pool get-quota rbd # # rbd is the name of Pool quotas for pool 'rbd': max objects: max bytes A: max bytes A

Set quotas for pool

Delete the operation of a pool

Ceph osd pool delete vm vm-yes-i-really-really-mean-it # vm is the name of pool. Thank you for reading! This is the end of this article on "sample Analysis of ceph pool Management in docker". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!