Search

Chapter 6. Recommended Minimum Hardware

download PDF

Ceph can run on non-proprietary commodity hardware. Small production clusters and development clusters can run without performance optimization with modest hardware.

ProcessCriteriaMinimum Recommended

ceph-osd

Processor

1x AMD64 or Intel 64

Nodes

Minimum of three nodes required.

RAM

For FileStore OSDs, Red Hat typically recommends a baseline of 16 GB of RAM per OSD host, with an additional 2 GB of RAM per daemon. For BlueStore OSDs, Red Hat typically recommends a baseline of 16 GB of RAM per OSD host, with an additional 5 GB of RAM per daemon.

OS Disk

1x OS disk per host

Volume Storage

1x storage drive per daemon

Journal

Optionally, 1x SSD partition per daemon

block.db

Optional, but Red Hat recommended, 1x SSD or NVMe or Optane partition or lvm per daemon. Sizing is 4% of block.data for BlueStore

block.wal

Optionally, 1x SSD or NVMe or Optane partition or logical volume per daemon. Use a small size, for example 10 GB, and only if it’s faster than the block.db device.

Network

2x 1GB Ethernet NICs

ceph-mon

Processor

1x AMD64 or Intel 64

Nodes

Minimum of three nodes required.

RAM

1 GB per daemon

Disk Space

10 GB per daemon (50 GB recommended)

Monitor Disk

1x SSD disk for leveldb monitor data (optional)

Network

2x 1 GB Ethernet NICs

ceph-radosgw

Processor

1x AMD64 or Intel 64

RAM

1 GB per daemon

Disk Space

5 GB per daemon

Network

1x 1 GB Ethernet NICs

ceph-mds

Processor

1x AMD64 or Intel 64

RAM

2 GB per daemon

This number is highly dependent on the configurable MDS cache size. The RAM requirement is typically twice as much as the amount set in the mds_cache_memory_limit configuration setting. Note also that this is the memory for your daemon, not the overall system memory.

Disk Space

2 MB per daemon, plus any space required for logging, which might vary depending on the configured log levels

Network

2x 1 GB Ethernet NICs

Note that this is the same network as the OSDs. If you have a 10 GB network on your OSDs you should use the same on your MDS so that the MDS is not disadvantaged when it comes to latency.

Additional Resources

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.