rack-affinity · shipping · also rack affinity (failure analysis)

Rack affinity

Rack affinity ranks the rack concentration of a failure burst against same-size random bursts in the same storage cell.

For affected-node counts k_i per rack, the raw score R = sum k_i(k_i - 1)/2 counts same-rack pairs. Affinity is P(R_random < R) + 0.5 P(R_random = R), where the reference uniformly selects the same number of distinct nodes without replacement from the same cell. The half-tie term gives the random reference a mean affinity of 0.5; individual random bursts need not have that value. The score and affinity are distinct quantities. [1]

High affinity does not establish a whole-rack power or network outage. Ford et al. describe partial-rack events compatible with component batches or software changes. It is a concentration ranking, not a failure rate or a posterior probability of a shared cause. [1]

Hesela's exact fictional four-node example gives same-rack affinity 5/6 for capacities [2, 2] but 3/4 for [3, 1], holding the two-node burst size fixed. In the first topology, 1 - affinity is 1/6 while the inclusive upper-tail probability is 1/3 because of ties. These are constructed arithmetic results, not fleet measurements. [2]

A neutral affinity does not establish independent failures or low outage severity. In Hesela's same four-node cell, a burst affecting all four nodes has score 2 but affinity 1/2. Its reference contains one subset, so every score ties, even if a shared outage made every node unavailable. Record burst size and observed service impact separately; this constructed result does not determine data loss or outage duration. [2]

Relations

related
Failure burst, Failure domain, CRUSH

Citations

  1. Ford et al., Availability in Globally Distributed Storage Systems, OSDI 2010, section 4.3, printed pages 6-7 (accessed 2026-11-09)
  2. Hesela: rack concentration, tied scores and an exact illustrative enumeration (accessed 2026-11-09)
Sources & caveats
  • Full paper section 4.3 read via https://www.cs.albany.edu/~jhh/courses/readings/ford10.osdi10.availability.pdf on 2026-11-09; canonical publisher URL retained.
  • The four-node example and inclusive-tail comparison are Hesela derivations; no Google trace was reanalyzed.
  • Whole-cell boundary added and independently checked on 2026-11-10; conditional concentration is not an outage-severity measure.

JSON: /data/terms/rack-affinity.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Rack affinity. Hesela. 2026-11-10. https://hesela.dev/terms/rack-affinity/