forked from docs/doc-exports
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: zhengxiu <zhengxiu@huawei.com> Co-committed-by: zhengxiu <zhengxiu@huawei.com>
17 lines
1.3 KiB
HTML
17 lines
1.3 KiB
HTML
<a name="EN-US_TOPIC_0000001933318526"></a><a name="EN-US_TOPIC_0000001933318526"></a>
|
|
|
|
<h1 class="topictitle1">What Do I Do If the Average Memory Usage of a CSS Cluster Reaches 98%?</h1>
|
|
<div id="body0000001475377077"><div class="section" id="EN-US_TOPIC_0000001933318526__section4498115716342"><h4 class="sectiontitle">Symptom</h4><p id="EN-US_TOPIC_0000001933318526__p13401459153412">The cluster monitoring result shows that the average memory usage of a cluster is 98%. Does it affect cluster performance?</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001933318526__section1621791003713"><h4 class="sectiontitle">Possible Cause</h4><p id="EN-US_TOPIC_0000001933318526__p471415117378">In an Elasticsearch cluster, 50% of the memory is occupied by Elasticsearch and the other 50% is used by Lucene to cache files. It is normal that the average memory usage reaches 98%.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001933318526__section195145994011"><h4 class="sectiontitle">Solution</h4><p id="EN-US_TOPIC_0000001933318526__p201311032164118">You can monitor the cluster memory usage by checking the maximum JVM heap usage and average JVM heap usage.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0148.html">CSS Cluster Monitoring and O&M</a></div>
|
|
</div>
|
|
</div>
|
|
|