forked from docs/doc-exports
zhengxiu
93d856d5c5
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: zhengxiu <zhengxiu@huawei.com> Co-committed-by: zhengxiu <zhengxiu@huawei.com>
24 lines
2.8 KiB
HTML
24 lines
2.8 KiB
HTML
<a name="EN-US_TOPIC_0000001936831250"></a><a name="EN-US_TOPIC_0000001936831250"></a>
|
|
|
|
<h1 class="topictitle1">How Do I Query the Index Size on OBS After the Freezing of Indexes for a CSS Cluster?</h1>
|
|
<div id="body0000001936831250"><p id="EN-US_TOPIC_0000001936831250__p13285164711013">The size of indexes remains unchanged after freezing. By querying the size of frozen indexes in OBS, you obtain the size of all indexes stored on OBS.</p>
|
|
<div class="p" id="EN-US_TOPIC_0000001936831250__p84896115272">Run the following command to obtain information about all indexes that are being frozen or have already been frozen:<pre class="screen" id="EN-US_TOPIC_0000001936831250__en-us_topic_0000001223594408_screen111712156459">GET _cat/freeze_indices?stage=$</pre>
|
|
</div>
|
|
<p id="EN-US_TOPIC_0000001936831250__en-us_topic_0000001223594408_p16515114484418">The output is as follows (as an example only):</p>
|
|
<pre class="screen" id="EN-US_TOPIC_0000001936831250__en-us_topic_0000001223594408_screen1056385184511">green open data2 0bNtxWDtRbOSkS4JYaUgMQ 3 0 5 0 7.9kb 7.9kb
|
|
green open data3 oYMLvw31QnyasqUNuyP6RA 3 0 51 0 23.5kb 23.5kb</pre>
|
|
<p id="EN-US_TOPIC_0000001936831250__p44779262286">The last column of the returned result contains the index size information.</p>
|
|
<p id="EN-US_TOPIC_0000001936831250__p176665916568"><strong id="EN-US_TOPIC_0000001936831250__b1913516427562">Related Questions</strong></p>
|
|
<ul id="EN-US_TOPIC_0000001936831250__ul360671816569"><li id="EN-US_TOPIC_0000001936831250__li1611222914569"><strong id="EN-US_TOPIC_0000001936831250__b494102975715">Billing for index storage on OBS</strong><p id="EN-US_TOPIC_0000001936831250__p171489153317">Storing index data in OBS incurs additional charges.</p>
|
|
</li><li id="EN-US_TOPIC_0000001936831250__li060610185569"><strong id="EN-US_TOPIC_0000001936831250__b16667423563">Why are frozen indexes stored in OBS still searchable via commands?</strong><p id="EN-US_TOPIC_0000001936831250__p17166438162919">Elasticsearch and OpenSearch clusters use local storage by default, and Lucene index files are stored on local disks. Lucene interacts with the underlying storage via the Directory API. Files can be read through the following API:</p>
|
|
<pre class="screen" id="EN-US_TOPIC_0000001936831250__screen11662038192914">public abstract IndexInput openInput(String name, IOContext context) throws IOException;</pre>
|
|
<p id="EN-US_TOPIC_0000001936831250__p10166153812292">The storage-compute decoupling feature enables interaction with OBS through the Directory API to read files stored in OBS. This is why information about frozen indexes stored in OBS can be queried using commands.</p>
|
|
</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0137.html">Managing CSS Clusters</a></div>
|
|
</div>
|
|
</div>
|
|
|