Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
PWL NY: Simple Testing Can Prevent Most Critica...
Search
Caitie McCaffrey
June 14, 2016
Technology
8
420
PWL NY: Simple Testing Can Prevent Most Critical Failures
Caitie McCaffrey
June 14, 2016
Tweet
Share
More Decks by Caitie McCaffrey
See All by Caitie McCaffrey
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
327
21k
The Path Towards Simplifying Consistency in Distributed Systems
caitiem20
1
260
Argus Papers We Love
caitiem20
13
1.1k
The Verification of a Distributed System
caitiem20
22
2.2k
We Hear You Like Papers: Eventual Consistency
caitiem20
14
760
The Verification of a Distributed System
caitiem20
12
720
The Verification of a Distributed System
caitiem20
6
730
A Brief History of Distributed Programming: RPC
caitiem20
31
6.4k
Building Scalable Stateful Services
caitiem20
12
1.5k
Other Decks in Technology
See All in Technology
Efficient zero-copy networking using io_uring
ennael
PRO
0
380
リスクから学ぶKubernetesコンテナセキュリティ/k8s-risk-and-security
mochizuki875
1
330
Oracle Base Database Service 技術詳細
oracle4engineer
PRO
5
48k
Slackbot × RAG で実現する社内情報検索の最適化
howdy39
2
340
ガバメントクラウド開発と変化と成長する組織 / Organizational change and growth in developing a government cloud
kazeburo
4
970
業務ヒアリングと知識の呪い
tamai_63
0
290
Vespaを利用したテクいベクトル検索
szdr
2
180
今こそ変化対応力を向上させるとき 〜ログラスが FAST に挑戦する理由〜 / Why Loglass is Talking on the Challenge of Agile Framework FAST
shioyang
0
120
Amplify Gen 2ではじめる 生成AIアプリ開発入門
tsukuboshi
0
220
Webセキュリティのあるきかた
akiym
32
11k
ファインディにおけるフロントエンド技術選定の歴史
puku0x
1
110
YAPC::Hakodateの映像記録を支える技術
godan
4
370
Featured
See All Featured
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
231
17k
BBQ
matthewcrist
85
9.2k
StorybookのUI Testing Handbookを読んだ
zakiyama
26
5.1k
Put a Button on it: Removing Barriers to Going Fast.
kastner
58
3.5k
Six Lessons from altMBA
skipperchong
26
3.4k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
355
29k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
31
2.6k
Designing for Performance
lara
604
68k
Git: the NoSQL Database
bkeepers
PRO
425
64k
Unsuck your backbone
ammeep
668
57k
Become a Pro
speakerdeck
PRO
24
4.9k
How to train your dragon (web standard)
notwaldorf
87
5.6k
Transcript
Simple Testing Can Prevent Most Critical Failures: An Analysis of
Production Failures in Distributed Data-Intensive Systems Papers We Love New York - June 2016
Caitie McCaffrey @caitie Distributed Systems Engineer CaitieM.com
None
None
Analyzed Failures in Real World Systems
“A majority (77%) of failures require more than one input
event to manifest, but most of the failures (90%) require no more than 3” Complexity of Failures
“The specific order of events is important in 88% of
the failures that require multiple events Complexity of Failures
“3 Nodes or less can reproduce 98% of Failures” Complexity
of Failures
Unit Tests “A majority of production failures (77%) can be
reproduced by a unit test”
Top Down Fault Injection & State Space Exploration is Expensive
Logging • 76% of the failures print explicit failure- related
error messages • For 84% of the failures, all of the triggering events are logged • Logs are noisy: each failure prints 824 log messages (median)
Catastrophic Failures
Error Handling • 92% of failures were the result of
incorrect handling of non-fatal errors • 58% of faults could have been detected via simple testing • 35% of failures caused by bad practices in error handling code
• Error Handling Code is simply empty or only contains
a Log statement • Error Handler aborts cluster on an overly general exception • Error Handler contains comments like FIXME or TODO Bad Practices
Aspirator Performs static analysis of Java bytecode to detect: •
error handler is empty • error handler over-catches exceptions and aborts • error handler contains phrases like “TODO” or “FIXME”
• 500 New Bugs & Bad Practices • 115 Fasle
Positives • 171 bugs reported • 143 bugs confirmed or fixed Aspirator Results
-developer “I fail to see the reason to handle every
exception” Developer Reactions
“It is often much harder to reason about the correctness
of a system’s abnormal path than its normal execution path ”
Moving Forward • Use a tool like Aspirator that is
capable of identifying trivial bugs • Enforce code reviews of error handling code • High code coverage on error handling code
Questions @caitie