Skip to content

Commit

Permalink
docs: recommend primary affinity over hybrid pools
Browse files Browse the repository at this point in the history
Hybrid pools suffer from lower availability when a node goes down,
so we recommend primary affinity instead of hybrid pools.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
  • Loading branch information
travisn committed Dec 17, 2021
1 parent 4c45856 commit 277252a
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions Documentation/ceph-pool-crd.md
Expand Up @@ -35,6 +35,10 @@ spec:
Hybrid storage is a combination of two different storage tiers. For example, SSD and HDD.
This helps to improve the read performance of cluster by placing, say, 1st copy of data on the higher performance tier (SSD or NVME) and remaining replicated copies on lower cost tier (HDDs).

**WARNING** Hybrid storage pools are likely to suffer from lower availability if a node goes down. The data across the two
tiers may actually end up on the same node, instead of being spread across unique nodes (or failure domains) as expected.
Instead of using hybrid pools, consider configuring [primary affinity](https://docs.ceph.com/en/latest/rados/operations/crush-map/#primary-affinity) from the toolbox.

```yaml
apiVersion: ceph.rook.io/v1
kind: CephBlockPool
Expand Down

0 comments on commit 277252a

Please sign in to comment.