Cluster size: 11 x X400 nodes (all 3TB NL-SAS SED drives)
Current Protection: +2:1
We are getting ready to add two more nodes and would like to change protection to +3. What is the best way to accomplish both tasks (cluster expansion and protection change) ? Should i join the two nodes first and them immediatly change protection ? Just trying to avoid un-nessary churn in terms of restripe.
I'm not sure if you can really do it in one restripe. Because there's two separate jobs involved here... smartpools/setprotectplus (to set the protection level), and multiscan/autobalance (to rebalance the nodes). My choice is usually to run the smartpools first, because it will move some data at least to the new nodes, but you'll also need to run a multiscan after that to get it truly balanced.
I agree with carlilek...if your cluster is relatively balanced before the 2 nodes are added then SmartPools/SetProtectPlus may keep it relatively balanced after completing its run. With 2 empty nodes, and a change in protection, expect to see full stripes of data and parity written across all 13 nodes. It's been my experience that this sort of change usually keeps the cluster relatively balanced so long as you don't go about deleting huge amounts of data in the middle of the restripe. So, add the nodes, change the protection level, let SP/SPP run and then (if needed), you can run MultiScan to finish balancing the cluster (and clearing orphaned blocks/inodes).
My understading, Peter, is that the multiscan will not make that restripe change until a smartpools has been run. So what I would do is add the nodes, cancel the automatic multiscan/autobalance, make the change in the smartpools interface, then run the smartpools job.
Peter, when you say "at some point" , what do you mean by that ? Goal is to avoid multiple restripes. So do i join both nodes to the cluster, immediately cancel autobalance job, go into pool properties and change protection to +3 and then start setprotect job manually ?
carlilek
2 Intern
•
205 Posts
679
1
Posted October 28th, 2015 09:00
I'm not sure if you can really do it in one restripe. Because there's two separate jobs involved here... smartpools/setprotectplus (to set the protection level), and multiscan/autobalance (to rebalance the nodes). My choice is usually to run the smartpools first, because it will move some data at least to the new nodes, but you'll also need to run a multiscan after that to get it truly balanced.