Page MenuHomePhabricator

cirrussearch: alert for tripping circuitbreakers
Open, Needs TriagePublic

Description

Consider if the alerting on tripping memory circuitbreaker is giving useful signal and debuggable. Seems like we had this kind of alert in the past, T355795.

We had circuitbreaker-related issues recently, investigating how to better alert

Event Timeline

atsuko renamed this task from Setup the alert for triggering circuitbreakers to cirrussearch: alert for tripping circuitbreakers.Jul 10 2026, 1:17 PM

Change #1309685 had a related patch set uploaded (by Atsuko; author: Atsuko):

[operations/alerts@master] cirrussearch: alert on tripped circuit breakers

https://gerrit.wikimedia.org/r/1309685

Change #1309685 merged by jenkins-bot:

[operations/alerts@master] cirrussearch: alert on tripped circuit breakers

https://gerrit.wikimedia.org/r/1309685

Alert is now acknowledged for a weekend and Monday while I'm drafting the runbook.

  1. Data in prometheus are corresponding to the GC events
  2. It doesn't correlate with Caused by: org.opensearch.core.common.breaker.CircuitBreakingException: [parent] Data too large, ..., which is larger than the limit of [30601641984/28.5gb]

I think this alert might be moderately useless.

Change #1309691 had a related patch set uploaded (by Atsuko; author: Atsuko):

[operations/alerts@master] Revert "cirrussearch: alert on tripped circuit breakers"

https://gerrit.wikimedia.org/r/1309691

atsuko changed the task status from In Progress to Open.EditedMon, Jul 13, 9:45 AM

Reverted the change, blocked on T324335.

Change #1309691 merged by jenkins-bot:

[operations/alerts@master] Revert "cirrussearch: alert on tripped circuit breakers"

https://gerrit.wikimedia.org/r/1309691