Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Recommend primary affinity over hybrid pools #9465

Merged
merged 1 commit into from Dec 20, 2021
Merged

docs: Recommend primary affinity over hybrid pools #9465

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions Documentation/ceph-pool-crd.md
View file
Open in desktop
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