copper/ccnet-prod-devops
1
0
Fork 0
Code Issues 23 Pull requests 2 Projects Releases Packages Wiki Activity Actions

osd.1 stuck BLUESTORE_SLOW_OP_ALERT counter #49

New issue
Open
opened 2026-08-10 22:09:09 +00:00 by claude-bot · 1 comment
claude-bot commented 2026-08-10 22:09:09 +00:00
Collaborator
Copy link

osd.1 (node02) carries a stale BLUESTORE_SLOW_OP_ALERT internal counter that does not clear on its own — confirmed zero actual slow-op journal entries in the last 24h as of 2026-08-08, currently muted (sticky) to keep cluster health clean. Cosmetic only, no data/performance impact. Fix: systemctl restart ceph-osd@1 on node02 to reset the internal counter, then ceph health unmute BLUESTORE_SLOW_OP_ALERT. See docs/homelab-build-history.md Item 16 for context (surfaced during the EC/hdd-bulk decommission cleanup).

osd.1 (node02) carries a stale BLUESTORE_SLOW_OP_ALERT internal counter that does not clear on its own — confirmed zero actual slow-op journal entries in the last 24h as of 2026-08-08, currently muted (sticky) to keep cluster health clean. Cosmetic only, no data/performance impact. Fix: `systemctl restart ceph-osd@1` on node02 to reset the internal counter, then `ceph health unmute BLUESTORE_SLOW_OP_ALERT`. See docs/homelab-build-history.md Item 16 for context (surfaced during the EC/hdd-bulk decommission cleanup).
claude-bot commented 2026-08-27 02:27:16 +00:00
Author
Collaborator
Copy link

2026-08-26: unmuted BLUESTORE_SLOW_OP_ALERT (ceph health unmute BLUESTORE_SLOW_OP_ALERT from node01). Cluster is now a clean HEALTH_OK with no mute — the alert is not currently re-firing, confirming it was a stuck/stale counter as this issue's title says, not a live slow-op condition. If it recurs it'll now surface as a real HEALTH_WARN again; leaving this issue open to watch for that over the next few days before closing.

2026-08-26: unmuted `BLUESTORE_SLOW_OP_ALERT` (`ceph health unmute BLUESTORE_SLOW_OP_ALERT` from node01). Cluster is now a clean `HEALTH_OK` with no mute — the alert is not currently re-firing, confirming it was a stuck/stale counter as this issue's title says, not a live slow-op condition. If it recurs it'll now surface as a real `HEALTH_WARN` again; leaving this issue open to watch for that over the next few days before closing.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
docs-emc-shelf-lcc-fan-finding
worktree-phase-0.5-appdata-pbs-backup
worktree-claude-md-migration
worktree-mosquitto-swarm-deploy
worktree-pbs-backup-migration
worktree-unraid-sas-shelf-bench
worktree-par2-integrity-doc
No results found.
Labels
Clear labels   
blocked
Waiting on something external before it can proceed

  
borg-backup
ccnet-borg-backup

  
ceph
Ceph pool/CephFS/mon work not tied to one stack

  
forgejo
ccnet-forgejo-swarm

  
in-progress
Actively being worked on right now

  
infra
OPNsense, Caddy, DNS, and other cross-cutting infra

  
netdata
ccnet-netdata-monitoring

  
nextcloud
ccnet-nextcloud-swarm

  
p:high
Should be picked up soon

  
p:low
No urgency, quality-of-life or deferred

  
p:medium
Worth doing, no fixed timeline

  
searxng
ccnet-searxng-swarm

  
service-onboard
ccnet-service_onboard

  
swarm-nodes
ccnet-swarm-nodes-runbook

No labels
blocked
borg-backup
ceph
forgejo
in-progress
infra
netdata
nextcloud
p:high
p:low
p:medium
searxng
service-onboard
swarm-nodes
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
copper/ccnet-prod-devops#49
No description provided.