How would you do a full data migration in a 2 node cluster? You don't have anywhere to migrate the data to?
Exactly, but that is the better of the 3 options if you are taking it offline for a few hours. My guess is that it is probably better to increase Repair Delay Timer, and then choose "Ensure Accessibility", but trying to get some feedback on the differences in a 2-node cluster.
1 person found this helpful
You can look at the following thread for more insight:
You can also increase the "repair delay time" if you're sure the host will take more than 60 minutes to come back:
Just in case, here you can find the consideration of moving into MM when using a 2 node cluster:
"I was thinking it should just be a copy(raid 1) between the 2 nodes, so why not always mark if as "full data migration"?"
With default Storage Policy (PFTT=1,FTM=RAID1) it keeps a replica of the data on each data-node - it wouldn't be beneficial (nor compliant with the Storage Policy) to move a second copy of the data to the other node (only have to clone it all back later).
"That way you can shut it down as long as needed without having to worry about the Repair Delay Timer, etc?"
In the case of hosts in MM with EA, you don't have to worry about CLOM repair delay in a 1+1+1 or 2+1 or even a standard 3-node cluster as if it expires, where exactly would it rebuild the components to be compliant with the Storage Policy?
It wouldn't as it wouldn't increase FTT nor compliance and thus just delta resync should occur (e.g. the data it did not commit while out of the loop).