<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>IO on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/io/</link><description>Recent content in IO on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Mon, 03 Jun 2024 21:00:16 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/io/atom.xml" rel="self" type="application/rss+xml"/><item><title>High-Frequency IO Pods Are Not Suited to Setting a Limit</title><link>https://www.chenshaowen.com/en/blog/high-frequency-io-pod-not-suitable-for-setting-limit.html</link><pubDate>Mon, 03 Jun 2024 21:00:16 +0000</pubDate><atom:modified>Mon, 03 Jun 2024 21:00:16 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/high-frequency-io-pod-not-suitable-for-setting-limit.html</guid><description>1. Symptoms Elasticsearch on Kubernetes was restarting frequently, leaving the service almost unusable.
During data import, the Pod&amp;rsquo;s memory usage kept growing Once the Pod&amp;rsquo;s memory usage approached the Limit, continued importing triggered an abnormal Pod exit, with the error log ERROR: Elasticsearch exited unexpectedly The Pod&amp;rsquo;s memory usage did not drop; it stayed near the Limit, and before long the Pod exited abnormally again The Elasticsearch Pod&amp;rsquo;s memory limit was 64GB, while the JVM memory limit was 32GB.</description><dc:creator>WeChat Official Account</dc:creator><category>IO</category><category>Kubernetes</category><category>Elasticsearch</category><category>Operations</category></item></channel></rss>