Help Center/ Cloud Search Service/ FAQs/ Managing CSS Clusters/ How Do I Query the Index Size on OBS After the Freezing of Indexes for a CSS Cluster?
Updated on 2024-09-14 GMT+08:00
View PDF
Share

How Do I Query the Index Size on OBS After the Freezing of Indexes for a CSS Cluster?

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.

Run the following command to obtain information about all indexes that are being frozen or have already been frozen: 
GET _cat/freeze_indices?stage=$

The output is as follows (as an example only):

green open data2 0bNtxWDtRbOSkS4JYaUgMQ 3 0  5 0  7.9kb  7.9kb
green open data3 oYMLvw31QnyasqUNuyP6RA 3 0 51 0 23.5kb 23.5kb

The last column of the returned result contains the index size information.

Related Questions

  • Billing for index storage on OBS

    Fees may be incurred when you store indexes in OBS. For details, see the price of standard single-AZ storage in OBS Price Calculator.

  • Why can frozen indexes stored in OBS still be queried using commands?

    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:

    public abstract IndexInput openInput(String name, IOContext context) throws IOException;

    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.

Parent topic: Managing CSS Clusters