

















D3N stands for Datacenter Data Delivery Network. It is a read cache layer built into the Ceph RADOS Gateway (RGW) that stores frequently accessed objects closer to the consumer. D3N was designed for multi-site deployments where data lives in a remote zone but clients in a local datacenter repeatedly read the same objects.
D3N operates as a transparent read-through cache. When an RGW receives a GET request:
Client --> RGW --> D3N Cache --> (hit) --> Client
--> (miss) --> Ceph RADOS --> cache --> ClientD3N uses the following key components:
D3N is most beneficial when:
It is less useful for write-heavy workloads or purely sequential one-time reads.
D3N is configured in the Ceph configuration file or via ceph config set:
# Enable D3N on a specific RGW instance
ceph config set client.rgw.myzone rgw_d3n_l1_local_datacache_enabled true
ceph config set client.rgw.myzone rgw_d3n_l1_datacache_persistent_path /var/lib/ceph/rgw/cache
ceph config set client.rgw.myzone rgw_d3n_l1_datacache_size 10737418240Or in ceph.conf:
[client.rgw.myzone]
rgw_d3n_l1_local_datacache_enabled = true
rgw_d3n_l1_datacache_persistent_path = /var/lib/ceph/rgw/cache
rgw_d3n_l1_datacache_size = 10737418240# Check D3N config settings
ceph config get client.rgw.myzone rgw_d3n_l1_local_datacache_enabled
# View RGW logs for D3N activity
journalctl -u [email protected] --no-pager | grep -i d3nD3N is a powerful read cache layer in Ceph RGW that reduces latency and bandwidth consumption by caching frequently accessed objects locally. It is especially valuable in multi-site deployments. Understanding its architecture - including cache backends, libaio for async I/O, and LRU eviction - is the foundation for tuning and monitoring D3N effectively in production.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。