Re:Initial details about why CrowdStrike's CSAgent.sys crashed
by phs318u on Sunday July 21, 2024 @09:01PM
(#41029931)
Bottom line is this: there is absolutely no good reason for not doing rolling updates. Do a few and make sure they are ok. Keep rolling out in groups. This single approach alone would've meant that this event was of marginal impact to most of the public, as sysadmins would've had the opportunity to halt further updates and work on remediating their first group (typically non-critical servers). Rolling out to everything all at once is just bad practice, period.
[ Parent
| on HN ]
Re:Initial details about why CrowdStrike's CSAgent.sys crashed
by hello_moto on Sunday July 21, 2024 @09:56PM
(#41030191)
Put yourself in the customer shoes: who wants to sign up to be rolled first?
There's best practice and then there's customer
Re:Initial details about why CrowdStrike's CSAgent.sys crashed
by RoyalHenOil on Tuesday July 23, 2024 @10:43AM
(#41046499)
Give those customers a discount.
The solution to customer reluctance to being the guinea pig is not to force every customer to be a guinea pig.