honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Expand How to tune for disk usage (#25562)

This commit is contained in:
Christoph Wurm 2017-08-21 12:07:54 -07:00 committed by GitHub
parent a48616272f
commit 0120448f76
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/reference/how-to/disk-usage.asciidoc
View File

@ -135,6 +135,13 @@ PUT index
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE
[float]
=== Watch your shard size
Larger shards are going to be more efficient at storing data. To increase the size of your shards, you can decrease the number of primary shards in an index by <<indices-create-index,creating indices>> with less primary shards, creating less indices (e.g. by leveraging the <<indices-rollover-index,Rollover API>>), or modifying an existing index using the <<indices-shrink-index,Shrink API>>.
Keep in mind that large shard sizes come with drawbacks, such as long full recovery times.
[float] [float]
=== Disable `_all` === Disable `_all`
@ -142,6 +149,11 @@ The <<mapping-all-field,`_all`>> field indexes the value of all fields of a
document and can use significant space. If you never need to search against all document and can use significant space. If you never need to search against all
fields at the same time, it can be disabled. fields at the same time, it can be disabled.
[float]
=== Disable `_source`
The <<mapping-source-field,`_source`>> field stores the original JSON body of the document. If you don’t need access to it you can disable it. However, APIs that needs access to `_source` such as update and reindex won’t work.
[float] [float]
=== Use `best_compression` === Use `best_compression`
@ -149,6 +161,18 @@ The `_source` and stored fields can easily take a non negligible amount of disk
space. They can be compressed more aggressively by using the `best_compression` space. They can be compressed more aggressively by using the `best_compression`
<<index-codec,codec>>. <<index-codec,codec>>.
[float]
=== Force Merge
Indices in Elasticsearch are stored in one or more shards. Each shard is a Lucene index and made up of one or more segments - the actual files on disk. Larger segments are more efficient for storing data.
The <<indices-forcemerge,`_forcemerge` API>> can be used to reduce the number of segments per shard. In many cases, the number of segments can be reduced to one per shard by setting `max_num_segments=1`.
[float]
=== Shrink Index
The <<indices-shrink-index,Shrink API>> allows you to reduce the number of shards in an index. Together with the Force Merge API above, this can significantly reduce the number of shards and segments of an index.
[float] [float]
=== Use the smallest numeric type that is sufficient === Use the smallest numeric type that is sufficient