cat segments APIedit

Returns low-level information about the Lucene segments in index shards, similar to the indices segments API.

For data streams, the API returns information about the stream’s backing indices.


GET /_cat/segments/<target>

GET /_cat/segments

Path parametersedit


(Optional, string) Comma-separated list of data streams, indices, and index aliases used to limit the request. Wildcard expressions (*) are supported.

To target all data streams and indices in a cluster, omit this parameter or use _all or *.

Query parametersedit

(Optional, byte size units) Unit used to display byte values.
(Optional, string) Short version of the HTTP accept header. Valid values include JSON, YAML, etc.

(Optional, string) Comma-separated list of column names to display.

If you do not specify which columns to include, the API returns the default columns in the order listed below. If you explicitly specify one or more columns, it only returns the specified columns.

Valid columns are:

index, i, idx
(Default) Name of the index, such as twitter.
shard, s, sh
(Default) Name of the shard.
prirep, p, pr, primaryOrReplica
(Default) Shard type. Returned values are primary or replica.
(Default) IP address of the segment’s shard, such as
(Default) Name of the segment, such as _0. The segment name is derived from the segment generation and used internally to create file names in the directory of the shard.
(Default) Generation number, such as 0. Elasticsearch increments this generation number for each segment written. Elasticsearch then uses this number to derive the segment name.
(Default) The number of documents as reported by Lucene. This excludes deleted documents and counts any nested documents separately from their parents. It also excludes documents which were indexed recently and do not yet belong to a segment.
(Default) The number of deleted documents as reported by Lucene, which may be higher or lower than the number of delete operations you have performed. This number excludes deletes that were performed recently and do not yet belong to a segment. Deleted documents are cleaned up by the automatic merge process if it makes sense to do so. Also, Elasticsearch creates extra deleted documents to internally track the recent history of operations on a shard.
(Default) Disk space used by the segment, such as 50kb.

(Default) Bytes of segment data stored in memory for efficient search, such as 1264.

A value of -1 indicates Elasticsearch was unable to compute this number.


(Default) If true, the segments is synced to disk. Segments that are synced can survive a hard reboot.

If false, the data from uncommitted segments is also stored in the transaction log so that Elasticsearch is able to replay changes on the next start.


(Default) If true, the segment is searchable.

If false, the segment has most likely been written to disk but needs a refresh to be searchable.

(Default) Version of Lucene used to write the segment.
(Default) If true, the segment is stored in a compound file. This means Lucene merged all files from the segment in a single file to save file descriptors.
ID of the node, such as k0zy.
(Optional, boolean) If true, the response includes help information. Defaults to false.
(Optional, string) Comma-separated list of column names or column aliases used to sort the response.
(Optional, boolean) If true, the response includes column headings. Defaults to false.


GET /_cat/segments?v

The API returns the following response:

index shard prirep ip        segment generation docs.count docs.deleted size size.memory committed searchable version compound
test  0     p _0               0          1            0  3kb        2042 false     true       8.6.0   true
test1 0     p _0               0          1            0  3kb        2042 false     true       8.6.0   true