[{"id":"IL-0376","title":{"en":"A maintenance update set off needless full syncs between Upstash Redis replicas in eu-west-1, slowing the databases","ko":"AWS eu-west-1 의 Upstash 리전 Redis 데이터베이스가 CPU 부하로 몇 시간 동안 느려졌다"},"org":"Upstash","org_slug":"upstash","date":"2025-02-25","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0376","shared_components":["cache"]},{"id":"IL-0217","title":{"en":"Honeycomb's main MySQL database locked up under cache-miss reads and ran out of connections, a 68-minute total outage","ko":"스키마 캐시가 데워지지 않아 주 MySQL 데이터베이스가 내부 교착에 빠지고 Honeycomb 전체가 68분 동안 멈췄다"},"org":"Honeycomb","org_slug":"honeycomb","date":"2023-07-25","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0217","shared_components":["cache"]},{"id":"IL-0295","title":{"en":"Pusher's Channels publish API on the mt1 cluster was largely unavailable for 11 minutes while a Redis master failed over","ko":"Pusher Channels mt1 클러스터의 메시지 발행 API 가 Redis 장애 조치 도중 11분 동안 거의 멈췄다"},"org":"Pusher","org_slug":"pusher","date":"2022-04-11","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0295","shared_components":["cache"]},{"id":"IL-0213","title":{"en":"Roblox was down for 73 hours because key-value writes on its single Consul cluster slowed from under 300 ms to 2 seconds","ko":"Consul 클러스터의 KV 쓰기가 느려지고 리더가 뒤처지며 Roblox 전체가 73시간 동안 멈췄다"},"org":"Roblox","org_slug":"roblox","date":"2021-10-28","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0213","shared_components":["cache"]},{"id":"IL-0041","title":{"en":"fluent-bit silently stopped shipping application logs from one node to Elasticsearch","ko":"fluent-bit 이 오류 없이 멈춰 운영 노드 한 대의 애플리케이션 로그가 Elasticsearch 로 전혀 가지 않았다."},"org":"PrometheusKube","org_slug":"prometheuskube","date":"2020-11-11","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0041","shared_components":["elasticsearch-opensearch"]},{"id":"IL-0279","title":{"en":"One failed Redis Cluster replica left only about 1 in 21 calls to Grab's Apollo service succeeding for a minute","ko":"Redis Cluster 의 슬레이브 노드 하나가 죽자 파이프라인 읽기가 실패해 Grab 의 운송 예약 서비스 Apollo 호출이 1분 동안 21번에 1번꼴로만 성공했다"},"org":"Grab","org_slug":"grab","date":"2019-02-15","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0279","shared_components":["cache"]},{"id":"IL-0277","title":{"en":"Patching Elastic Cloud's ZooKeeper ensemble in us-east-1 lost quorum, and hosted clusters and Kibana went unreachable","ko":"Elastic Cloud us-east-1 의 ZooKeeper 조정 계층이 쿼럼을 잃어 Elasticsearch 배포에 6시간 넘게 접속하지 못하고 Kibana 는 18:44 UTC 까지 불안정했다"},"org":"Elastic","org_slug":"elastic","date":"2019-02-04","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0277","shared_components":["elasticsearch-opensearch"]},{"id":"IL-0388","title":{"en":"A Google Cloud live migration took a Discord Redis primary offline, and the failover broke API instances and then guilds","ko":"Redis 고가용 클러스터의 primary 노드가 내려간 뒤 Discord API 가 느려지고 길드 일부가 오프라인으로 보이며 접속이 실패했다"},"org":"Discord","org_slug":"discord","date":"2017-10-13","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0388","shared_components":["cache"]},{"id":"IL-0274","title":{"en":"GitHub's code search Elasticsearch cluster hit near-100% CPU and rapid master elections; a restart found lost shards","ko":"GitHub 코드 검색의 elasticsearch 클러스터에서 일부 노드 CPU 가 100% 에 가깝게 차고 마스터가 계속 바뀌면서 검색과 색인이 타임아웃되고 샤드 데이터가 사라졌다"},"org":"GitHub","org_slug":"github","date":"2013-01-24","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0274","shared_components":["elasticsearch-opensearch"]}]