3 ms·
> Unfortunately, last Tuesday’s update contained a regular expression that backtracked enormously and exhausted CPU used for HTTP/HTTPS serving. One of those c
by woliveirajr 7y ago
> Unfortunately, last Tuesday’s update contained a regular expression that backtracked enormously and exhausted CPU used for HTTP/HTTPS serving.
One of those cases where they had 1 problem, used regular expression and ended up with 2 problems ?
Edit: I really like how much information is given by CloudFlare. 11 points in the "what went wrong analysis" is how every root-cause analysis should be done.
- toomuchtodo 7y agoSomewhat humorous, as someone [1] (congrats /u/fossuser!) mentioned this failure scenario in the thread about Twitter being down yesterday. "Pushing bad regex to production, chaos monkey code causing cascading network failure, etc.", in response to a comment from someone who previously worked at Cloudflare. [1] https://news.ycombinator.com/item?id=20415608 https://news.ycombinator.com/item?id=20415608
- citruspi 7y agoThey mentioned it was a regular expression in the original post[0] on the day of the incident, that part isn't news (discussion here[1]). [0]: https://blog.cloudflare.com/cloudflare-outage/ https://blog.cloudflare.com/cloudflare-outage/ [1]: https://news.ycombinator.com/item?id=20336332 https://news.ycombinator.com/item?id=20336332
- deleted 7y ago[deleted]
- anoviceuser 7y agoI agree this is an awesome post and a really great example of how every Root Cause Analysis needs to be done. I am also impressed by their incident response.