Default to not using compound file format for the index (increases number of open files, but faster indexing and recovery) #384
Labels
Comments
|
Default to not using compound file format for the index (increases number of open files, but faster indexing and recovery), closed by 485f904. |
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…c#384) MPC-4171: adding bruce & kostiantyn sandbox * MPC-4171: adding bruce & kostiantyn sandbox * Merge remote-tracking branch 'origin/master' into dev/igor/MPC-4171-adding-bruce-sandbox * Drop eks service url tags as we exceed 50 tag limits on ec2 * update nikita creds Approved-by: Can Yildiz
costin
pushed a commit
that referenced
this issue
Dec 6, 2022
This PR adds support for extracting keyword fields from doc values to ValuesSourceReaderOperator.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The title says it all. The increase should be around 5x number of open files per shard. Note, this is just open files for the index, not TCP connections.
In order to bring it back, set
index.merge.policy.use_compound_filetotrue.The text was updated successfully, but these errors were encountered: