Skip to main content
System Design7 min read

Post-Mortem: How a 2-Line Config Change Brought Down Our Search Cluster for 42 Minutes

At 14:02 UTC on a Tuesday, our search cluster stopped responding. Here is how an innocent thread pool config change killed node 3.

Post-Mortem: How a 2-Line Config Change Brought Down Our Search Cluster for 42 Minutes Cover

The Root Cause

We had modified search thread pool queue size from 1000 to unbounded in an attempt to prevent request rejection under traffic spikes.

SHARE ARTICLE

About the author

developerOS

The official developerOS team account.

Keep reading

Insights has no comments. See more from this author, browse the topic, or get new articles by email.

Explore More

Read Next on Insights

More in System Design
DeveloperOS Insider

Join the Insights Newsletter

Get direct engineering insights, Cloud tutorials, career prep guidebooks, and system design breakdown analyses sent straight to your inbox.