When Solid State Drives Are Not That Solid

Re:When Solid State Drives Are Not That Solid by kbar13 on Monday June 15, 2015 @09:35PM (#9723318)

if one machine failed and failover kicked in correctly, why was the engineer paged?

[ Parent | on HN ]

Re:When Solid State Drives Are Not That Solid by jimrandomh on Tuesday June 16, 2015 @12:23AM (#9723804)

Because it's hard to make an automatic monitoring system that reliably distinguishes between "a failure occurred but everything is fine" and "a failure occurred and now everything is on fire".

[ Parent | on HN ]

Re:When Solid State Drives Are Not That Solid by InclinedPlane on Monday June 15, 2015 @10:11PM (#9723424)

Depends on how much spare capacity they had. Being one failure away from going down is an emergency situation at many places.

[ Parent | on HN ]

Re:When Solid State Drives Are Not That Solid by mentat on Monday June 15, 2015 @09:39PM (#9723330)

I wondered this as well. Valuing your engineers' sleep is important.

[ Parent | on HN ]

Re:When Solid State Drives Are Not That Solid by adamsurak on Tuesday June 16, 2015 @03:50AM (#9724303)

We have multiple different pages. In our cluster we have 3 machines and if one of them is unavailable because of broken network, we do not page. In this case the page came as an application error that the application was not able to cope with. When we have issue that we have seen before and the server can handle it on its own, we do not page.

[ Parent | on HN ]

Re:When Solid State Drives Are Not That Solid by Qantourisc on Tuesday June 16, 2015 @02:53AM (#9724163)

Also depends on how many machines you got running. If it's 2: do you really want to wait it out and risk the other one going to hell too ?

[ Parent | on HN ]