PLEASE NOTE: This document applies to v1.1 version and not to the latest stable release v1.5Documentation for other releases can be found by using the version selector in the left bottom of any doc page.
Ceph Block Pool CRD
Rook allows creation and customization of storage pools through the custom resource definitions (CRDs). The following settings are available for pools.
For optimal performance, while also adding redundancy, this sample will configure Ceph to make three full copies of the data on multiple nodes.
NOTE: This sample requires at least 1 OSD per node, with each OSD located on 3 different nodes.
Each OSD must be located on a different node, because the
failureDomain is set to
host and the
replicated.size is set to
apiVersion: ceph.rook.io/v1 kind: CephBlockPool metadata: name: replicapool namespace: rook-ceph spec: failureDomain: host replicated: size: 3 deviceClass: hdd
This sample will lower the overall storage capacity requirement, while also adding redundancy by using erasure coding.
NOTE: This sample requires at least 3 bluestore OSDs.
The OSDs can be located on a single Ceph node or spread across multiple nodes, because the
failureDomain is set to
osd and the
erasureCoded chunk settings require at least 3 different OSDs (2
dataChunks + 1
apiVersion: ceph.rook.io/v1 kind: CephBlockPool metadata: name: ecpool namespace: rook-ceph spec: failureDomain: osd erasureCoded: dataChunks: 2 codingChunks: 1 deviceClass: hdd
High performance applications typically will not use erasure coding due to the performance overhead of creating and distributing the chunks in the cluster.
When creating an erasure-coded pool, it is highly recommended to create the pool when you have bluestore OSDs in your cluster (see the OSD configuration settings. Filestore OSDs have limitations that are unsafe and lower performance.
name: The name of the pool to create.
namespace: The namespace of the Rook cluster where the pool is created.
replicated: Settings for a replicated pool. If specified,
erasureCodedsettings must not be specified.
size: The desired number of copies to make of the data in the pool.
erasureCoded: Settings for an erasure-coded pool. If specified,
replicatedsettings must not be specified. See below for more details on erasure coding.
dataChunks: Number of chunks to divide the original object into
codingChunks: Number of coding chunks to generate
failureDomain: The failure domain across which the data will be spread. This can be set to a value of either
hostbeing the default setting. A failure domain can also be set to a different type (e.g.
rack), if it is added as a
locationin the Storage Selection Settings.
replicatedpool of size
3is configured and the
failureDomainis set to
host, all three copies of the replicated data will be placed on OSDs located on
3different Ceph hosts. This case is guaranteed to tolerate a failure of two hosts without a loss of data. Similarly, a failure domain set to
osd, can tolerate a loss of two OSD devices.
If erasure coding is used, the data and coding chunks are spread across the configured failure domain.
NOTE: Neither Rook, nor Ceph, prevent the creation of a cluster where the replicated data (or Erasure Coded chunks) can be written safely. By design, Ceph will delay checking for suitable OSDs until a write request is made and this write can hang if there are not sufficient OSDs to satisfy the request.
deviceClass: Sets up the CRUSH rule for the pool to distribute data only on the specified device class. If left empty or unspecified, the pool will use the cluster’s default CRUSH root, which usually distributes data over all OSDs, regardless of their class.
crushRoot: The root in the crush map to be used by the pool. If left empty or unspecified, the default root will be used. Creating a crush hierarchy for the OSDs currently requires the Rook toolbox to run the Ceph tools described here.
Erasure coding allows you to keep your data safe while reducing the storage overhead. Instead of creating multiple replicas of the data, erasure coding divides the original data into chunks of equal size, then generates extra chunks of that same size for redundancy.
For example, if you have an object of size 2MB, the simplest erasure coding with two data chunks would divide the object into two chunks of size 1MB each (data chunks). One more chunk (coding chunk) of size 1MB will be generated. In total, 3MB will be stored in the cluster. The object will be able to suffer the loss of any one of the chunks and still be able to reconstruct the original object.
The number of data and coding chunks you choose will depend on your resiliency to loss and how much storage overhead is acceptable in your storage cluster. Here are some examples to illustrate how the number of chunks affects the storage and loss toleration.
|Data chunks (k)||Coding chunks (m)||Total storage||Losses Tolerated||OSDs required|
failureDomain must be also be taken into account when determining the number of chunks. The failure domain determines the level in the Ceph CRUSH hierarchy where the chunks must be uniquely distributed. This decision will impact whether node losses or disk losses are tolerated. There could also be performance differences of placing the data across nodes or osds.
host: All chunks will be placed on unique hosts
osd: All chunks will be placed on unique OSDs
If you do not have a sufficient number of hosts or OSDs for unique placement the pool can be created, although a PUT to the pool will hang.
Rook currently only configures two levels in the CRUSH map. It is also possible to configure other levels such as
rack with the Ceph tools.