Chris LuandGitHub 506ce0850b telemetry: count erasure-coded volumes in the reported totals (#10632) ...

collectVolumeStats walked only DataNode.GetVolumes(), which returns the
regular volumes on each disk. An encoded volume leaves that set and is
reported through GetEcShards instead, so total_disk_bytes and
total_volume_count silently excluded every erasure-coded volume: a cluster
that encoded everything reported zero bytes and zero volumes while still
counting as a volume server.

Sum each holder's shard sizes into the byte total, parity and extra copies
included, matching how a replicated volume's used size counts every replica
and how CollectionEcVolumeStats already reports EC footprint. Count volume
ids rather than shard entries, since one volume's shards are spread over
many nodes and would otherwise multiply the volume count by the number of
holders.

2026-08-07 17:08:15 -07:00

..

client.go

Prevent split-brain: Persistent ClusterID and Join Validation (#8022)

2026-01-18 14:02:34 -08:00

collector_test.go

telemetry: count erasure-coded volumes in the reported totals (#10632)

2026-08-07 17:08:15 -07:00

collector.go

telemetry: count erasure-coded volumes in the reported totals (#10632)

2026-08-07 17:08:15 -07:00