As yet we have no design or implementation for taking over or resuming sagas when a Nexus instance become partitioned or otherwise offline for an extended period. That means a single failure could cause various rack activities to hang (provisions, upgrades, etc.). RFD 289 puts some constraints on this but doesn't say much else about it.
As yet we have no design or implementation for taking over or resuming sagas when a Nexus instance become partitioned or otherwise offline for an extended period. That means a single failure could cause various rack activities to hang (provisions, upgrades, etc.). RFD 289 puts some constraints on this but doesn't say much else about it.