---
title: "Discussion on \"\nWhy etcd Disk I/O Stalls Crash Your K8s Pods\" | Hashnode"
description: "Discussion on \"\nWhy etcd Disk I/O Stalls Crash Your K8s Pods\". How DIsk I/O stall impacted our production K8s  cluster"
url: "https://hashnode.com/posts/why-etcd-disk-i-o-stalls-crash-your-k8s-pods/6a408e171ad442b3923bb5c1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why etcd Disk I/O Stalls Crash Your K8s Pods](https://abhishekpareek.dev/why-etcd-disk-i-o-stalls-crash-your-k8s-pods?utm_source=hashnode&utm_medium=feed)

How DIsk I/O stall impacted our production K8s cluster

Feb 4 · 8 min read · abhishekpareek.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#etcd](https://hashnode.com/tag/etcd)
-   [#k8s](https://hashnode.com/tag/k8s)
-   [#etcd-performance](https://hashnode.com/tag/etcd-performance)
-   [#diskio](https://hashnode.com/tag/diskio)
-   [#fsync-latency](https://hashnode.com/tag/fsync-latency)

## Written by

[abhishek pareek](https://hashnode.com/@abhishek-pareek)

@abhishek-pareek · Vancouver, Canada

  
[View profile](https://hashnode.com/@abhishek-pareek)

Architecting resilient distributed systems by balancing throughput, reliability, and the trade-offs that matter at scale.

Senior engineer with 10+ years of experience designing, operating, and evolving production Kubernetes platforms and distributed systems. I make architectural decisions with a clear understanding of the operational tradeoffs and take ownership of the outcomes. My current work focuses on large-scale Kubernetes platforms and AI infrastructure, while I continue to explore agentic AI to accelerate thinking for more intelligent, reliable, and impactful platform operations. Based in Vancouver.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.