Affinity-aware allocation replacement in Nomad rolling updates
Migrating a small type = service application across heterogeneous node groups using Nomad's rolling update mechanism requires preserving application-local state without triggering temporary downtime. When dispatch = rolling replaces old allocations, the interaction between reschedule behavior, node affinity constraints, and min_healthy_percentage evaluation