<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>elasticsearch on www@aranciaga</title>
    <link>https://aranciaga.com/tags/elasticsearch/</link>
    <description>Recent content in elasticsearch on www@aranciaga</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 May 2024 01:34:00 -0300</lastBuildDate><atom:link href="https://aranciaga.com/tags/elasticsearch/atom.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Flood Stage Watermark in ElasticSearch</title>
      <link>https://aranciaga.com/posts/flood-stage-watermark-in-elasticsearch/</link>
      <pubDate>Wed, 01 May 2024 01:34:00 -0300</pubDate>
      
      <guid>https://aranciaga.com/posts/flood-stage-watermark-in-elasticsearch/</guid>
      <description>A watermark is simply a threshold set on a ElasticSearch cluster. In this case, **Flood Stage Watermark is indicating a major disk space issue**, 3 watermarks are related to that: low: 85% of disk usage (default) high: 90% of disk usage (default) flood_stage: 95% of disk usage (default) &amp;lt;- critical All watermarks can be verified running a GET requests to the cluster:
curl -X GET -H &amp;#34;Content-Type: application/json&amp;#34; http://[ENDPOINT]:9200/_cluster/settings?include_defaults=true When the last threshold or watermark is reached, ElasticSearch will force read-only mode.</description>
    </item>
    
  </channel>
</rss>
