The wild-card query that locked down our main search cluster

by•

Was writing a quick dev query to test substring matching on a customer search endpoint. Didn't realize I left a un-indexed leading wildcard on a text field across millions of documents.

The query executed globally, pinned CPU usage at 100% across every node, and brought the entire search bar down for 15 minutes while the cluster struggled to build a giant un-cached response.

2 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.