Rebalancing IO Overhead
What is the best way to handle the IO overhead of rebalance operations? Are there best practices about when to rebalance & how to prevent the rebalancing IO overhead from degrading the performance of storing new data to Swift? I know that Swift should never be over 80% full, so I would assume expansion should be planned around 70% full so that the rebalance operation can slowly move data over to the new nodes without reaching 80%?
As an example, lets consider a system with 1000 2TB devices spread over 20 machines. Lets say that data has been evenly stored data over all 1000 devices, such that they are all about 70% full. Would it be reasonable to acquire 200 more devices (also 2TB) and rebalance? Or should the minimum growth size be a larger percentage of the whole to make rebalancing less problematic?
The documentation I have seen so far talks about 1GB nics for the internal storage network. Is this a bottleneck during rebalancing? Or are the 1 GB nics sufficient for this task?
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Florian Hines
- Solved:
- Last query:
- Last reply: