<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Uday K</title><link>https://uday.dev/tags/debugging/</link><description>Recent content in Debugging on Uday K</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 20 Dec 2024 06:38:35 -0400</lastBuildDate><atom:link href="https://uday.dev/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Debugging Memory Exhaustion in a Kubernetes Redis Cluster</title><link>https://uday.dev/posts/redis-cache/</link><pubDate>Fri, 20 Dec 2024 06:38:35 -0400</pubDate><guid>https://uday.dev/posts/redis-cache/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;In one of our high-traffic deployments, which sits at the intersection of web and AI use cases, we had a Redis cache pod shared between the web application and AI background workers. While this setup wasn’t ideal, it had worked well—until one day, we were paged: Redis was down‼️ When a Redis pod crashes or restarts frequently, it&amp;rsquo;s important to follow a step-by-step guide to diagnose and resolve the root cause effectively.&lt;/p&gt;</description></item></channel></rss>