seen from Georgia
seen from China
seen from United States
seen from United States
seen from Malaysia
seen from United States
seen from United States
seen from United States
seen from South Korea
seen from China
seen from Germany
seen from South Korea
seen from China
seen from China
seen from Georgia
seen from United States
seen from Indonesia
seen from United States
seen from Brunei
seen from France
Paradox of Stability and Corruption in Systems
By: Fatima Winniclare Jayme The main goal of a fault-tolerant system is to provide continuity, reliability and regularity. But we must be careful to distinguish fault tolerance from issue solving. Fault tolerance is the question of “How can the system still work when there is a failure?” Answers to problem resolution ask a new question: “How can the causes of those failures be eliminated? It is…
Answer: Do I need a second RAID controller for fault-tolerance? #programming #computers #solution
Answer: Do I need a second RAID controller for fault-tolerance? #programming #computers #solution
Do I need a second RAID controller for fault-tolerance?
I have a server with 3 hard drives installed, and a total capacity of 6. We’re planning to max it out, but our consultant also suggested getting a second RAID controller “for redundancy” to support the new drives. To me, this doesn’t make much sense. Even with a second RAID controller running half of the disks, we’re still stuck with only…
View On WordPress
How-to: Fault-tolerant NFS? #computers #dev #programming
How-to: Fault-tolerant NFS? #computers #dev #programming
Fault-tolerant NFS?
Probably a FAQ but I haven’t found anything useful after a while of searching:
Can I set up NFS in such a way that every single error (e.g. server CPU, hard disk, hd controller, network adapter, network cable, power supply) is masked without any need for immediate intervention?
I have only answers for parts of the problem: RAID, redundant power supply, redundant network…
View On WordPress
Why would anyone use Netflix’s Chaos Monkey?
Failures happen and they inevitably happen when least desired or expected. If your application can’t tolerate an instance failure would you rather find out by being paged at 3am or when you’re in the office and have had your morning coffee? Even if you are confident that your architecture can tolerate an instance failure, are you sure it will still be able to next week? How about next month? Software is complex and dynamic and that “simple fix” you put in place last week could have undesired consequences. Do your traffic load balancers correctly detect and route requests around instances that go offline? Can you reliably rebuild your instances? Perhaps an engineer “quick patched” an instance last week and forgot to commit the changes to your source repository?
GitHub repository is here
Original title and link: The Best Defense Against Major Unexpected Failures Is to Fail Often: Netflix Open Sources Chaos Monkey (NoSQL database©myNoSQL)
