Overview

We experienced a service disruption in our production environment, specifically impacting the Redis memory usage in our freemium offering.

What was the issue?

The core of the issue was the Redis memory in prod2 (freemium) reaching near full capacity. This led to operational failures in dependent services, primarily due to Redis running out of memory (OOM). The root cause analysis identified a significant increase in memory consumption by one of the Redis streams (named freemium:streams:DEBEZIUM_idpMongo.idp-harness.backstageCatalog), which started consuming an unusually high amount of memory (~6 GB) following the latest release of the idp-service (version 1.6.0). Furthermore, pipeline service-related caches were also found to be consuming higher memory than anticipated.

Timeline

Resolution

The immediate resolution involved increasing the memory allocated to the Redis events framework database by 25% and disabling the stream flow that was consuming excessive memory. This action effectively resolved the incident within two hours.

Action Items

Following this incident, we are taking several steps to prevent recurrence:

• Implement rigorous validation of changes with respect to Redis memory usage in both QA and PROD environments with each release.
• Investigate and rectify the increased message size issue in the backstageCatalog stream when published to Redis.
• Establish alerts for individual streams to promptly notify the relevant teams.
• The Pipeline team will conduct a thorough review of streams related to their services, including the webhook_events_stream and git_push_event_stream.