For example, Google's Map Reduce paper has a section on fault tolerance that goes into detail about how they handle the issue of failing workers:
For example, Google's Map Reduce paper has a section on fault tolerance that goes into detail about how they handle the issue of failing workers:
This could be minimal and something that in terms of budgetary considerations might be negligible - but I'm not sure.
I think the calculation is replacing one drive takes about 15 minutes of work. If we have 30,000 drives and 2 percent fail, it takes 150 hours to replace those. In other words, one employee for one month of 8 hour days. Getting the failure rate down to 1 percent means you save 2 weeks of employee salary - maybe $5,000 total? The 30,000 drives costs you $4 million, so who cares about $5k here or there?
Is that really the true cost of replacement? I would think there is also the cost of dealing with the warranty and the testing and monitoring. Here is the quote from the blog post about unsuitable drives:
> When one drive goes bad, it takes a lot of work to get the RAID back on-line if the whole RAID is made up of unreliable drives. It’s just not worth the trouble.
I don't have the time to think about this fully, but it seems similar to calculating the present value of a future cash flow, because there are other costs beyond the first replacement effort:
> Their average age shows 0.8 years, but since these are warranty replacements, we believe that they are refurbished drives that were returned by other customers and erased, so they already had some usage when we got them.
It sounds like the total cost of a failed drive is actually 1.5x, because 50% of the replacement drives also fail.