Comment on HPE Drive fail at 32,768 hours without firmware updateparentComments−cesarb6yThat's only if the sysadmin was trusting a single server with the data, instead of a pair of redundant servers.Which were probably installed and started up at nearly the same time. Oops.This bug has the potential of simultaneously damaging whole sets of servers, if they were bought and installed in bulk. Dark day indeed.−abarringerOP6yWe have a cluster of four nodes that were all setup and brought online within hours of each other. The entire cluster could blow up within a couple hours if not patched.−Scoundreller6yI guess cluster nodes should be scheduled to be taken down for random amounts of time so that they fail in sequence more gracefully.Have an “off on weekends” node. And 24/7 nodes.
Comments
That's only if the sysadmin was trusting a single server with the data, instead of a pair of redundant servers.
Which were probably installed and started up at nearly the same time. Oops.
This bug has the potential of simultaneously damaging whole sets of servers, if they were bought and installed in bulk. Dark day indeed.
We have a cluster of four nodes that were all setup and brought online within hours of each other. The entire cluster could blow up within a couple hours if not patched.
I guess cluster nodes should be scheduled to be taken down for random amounts of time so that they fail in sequence more gracefully.
Have an “off on weekends” node. And 24/7 nodes.