It depends on the approach and how many LINs you have on the node.
If you're refreshing multiple nodes, create a separate storage pool from them and use SmartPools to offload the data. When the is almost all gone, then SmartFail the node - this can take 5-10 minutes.
For a large node with lots and lots of little files, it can take many days to SmartFail a node full of data.
Take the amount of time you need/expect it to take and multiply that by 20. That'll be your minimum.
But seriously, like Ed said, it depends on a number of things. I would also add the node type, metadata strategy, and used capacity of the other nodes in its pool.
I have seen an S class node fail out in a matter of hours. I have also seen an NL node in a pool that was >90% full take 2 weeks.
Anonymous User
170 Posts
1102
0
Posted November 29th, 2016 11:00
It depends on the approach and how many LINs you have on the node.
If you're refreshing multiple nodes, create a separate storage pool from them and use SmartPools to offload the data. When the is almost all gone, then SmartFail the node - this can take 5-10 minutes.
For a large node with lots and lots of little files, it can take many days to SmartFail a node full of data.