惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
Y
Y Combinator Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
The GitHub Blog
The GitHub Blog
N
Netflix TechBlog - Medium
MyScale Blog
MyScale Blog
F
Fortinet All Blogs
Microsoft Azure Blog
Microsoft Azure Blog
H
Help Net Security
C
Check Point Blog
博客园 - 聂微东
云风的 BLOG
云风的 BLOG
M
MIT News - Artificial intelligence
U
Unit 42
WordPress大学
WordPress大学
B
Blog
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
D
DataBreaches.Net
G
Google Developers Blog
T
The Blog of Author Tim Ferriss
Hugging Face - Blog
Hugging Face - Blog
IT之家
IT之家

OneUptime Blog

How to Monitor Azure App Services (PaaS) with OpenTelemetry Grafana Stack vs OneUptime: DIY Observability or Unified Platform? Your AI Workloads Are About to Blow Up Your Observability Bill The Great Observability Consolidation Is Here How to Write Custom Object Classes for Ceph How to Write Custom Ceph Manager Modules How to Write a ceph.conf Configuration File How to Use Rook-Ceph with OpenShift How to Use Rook-Ceph with Longhorn for Comparison How to Configure Volume Snapshot Class for RBD in Rook How to Configure VolumeReplicationClass Scheduling Intervals in Rook How to Set Up Volume Replication with Rook-Ceph How to Create Volume Group Snapshots with Rook CSI How to Visualize Ceph Network Performance in Grafana How to Enable Virtual Host-Style Bucket Access in Rook How to View Runtime Configuration via Admin Socket How to View Quota Settings and Update Stats in Ceph RGW How to View PG Scaling Recommendations with autoscale-status How to View PG Distribution via Admin Socket How to View Performance Metrics in the Ceph Dashboard How to View OSD Performance Counters in Ceph How to View Connection Status via Admin Socket How to View Ceph Cluster Summary Dashboard via CLI How to Version Control Rook-Ceph Configuration How to Version Control Ceph Infrastructure with Terraform How to Verify Kubernetes Node Requirements for Rook-Ceph Deployment How to Verify Health Before and After Rook Upgrades How to Verify Data Integrity with Deep Scrubbing How to Verify Complete Rook-Ceph Cleanup How to Verify Backup Integrity from Ceph Snapshots
How to Upgrade Ceph Clusters in Stretch Mode
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

Upgrade Considerations for Stretch Mode

Upgrading a Ceph cluster in stretch mode requires extra care because you must maintain quorum throughout the upgrade. Upgrading monitors or OSDs on both sites simultaneously can break quorum and cause a cluster-wide outage.

Pre-Upgrade Checklist

Before starting the upgrade, verify the cluster is healthy:

ceph status
ceph health detail
ceph osd stat
ceph mon stat

Ensure all PGs are active+clean:

ceph pg stat | grep "active+clean"

Set conservative flags to prevent rebalancing during the upgrade:

ceph osd set noout
ceph osd set noscrub
ceph osd set nodeep-scrub

Step 1 - Upgrade the Arbiter Monitor

Start with the arbiter since it has no OSDs and minimal impact on cluster operations:

ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 --daemon-types mon --hosts mon-arbiter

Monitor the upgrade:

ceph orch upgrade status

Wait for the arbiter to rejoin quorum:

ceph mon stat

Step 2 - Upgrade Site A Monitors

Upgrade the two monitors on site A one at a time:

ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 --daemon-types mon --hosts mon-dc1a

Wait for quorum:

ceph quorum_status

Then upgrade the second monitor on site A:

ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 --daemon-types mon --hosts mon-dc1b

Step 3 - Upgrade Site B Monitors

Repeat for site B monitors:

ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 --daemon-types mon --hosts mon-dc2a
ceph quorum_status
ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 --daemon-types mon --hosts mon-dc2b

Step 4 - Upgrade Managers

Upgrade MGR daemons:

ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 --daemon-types mgr

Step 5 - Upgrade OSDs by Site

Upgrade OSDs on site A first, then site B. This maintains data accessibility from at least one site:

# Upgrade site A OSDs
ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 \
  --daemon-types osd --hosts host-dc1a,host-dc1b

# Wait for PGs to recover
watch ceph pg stat

# Upgrade site B OSDs
ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.0 \
  --daemon-types osd --hosts host-dc2a,host-dc2b

Step 6 - Post-Upgrade Verification

After all daemons are upgraded, clear the maintenance flags:

ceph osd unset noout
ceph osd unset noscrub
ceph osd unset nodeep-scrub

Verify the cluster version and health:

ceph version
ceph status
ceph orch ps | grep -v "running"

Summary

Upgrading Ceph clusters in stretch mode requires a sequential per-site approach starting with the arbiter monitor. By upgrading monitors and OSDs site by site and waiting for quorum and PG health at each step, you maintain continuous availability throughout the upgrade process. Setting maintenance flags before starting prevents unnecessary rebalancing during the rolling upgrade.