honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-17 10:25:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

shrink may full copy when using multi data paths (#42913) (#42961)

Browse Source 
Additional scenario for full segment copy if hard link
cannot work across disks.
This commit is contained in:
James Baiera 2019-06-12 14:34:31 -04:00 committed by GitHub
parent b110164bf4
commit 51618af056
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/reference/indices/shrink-index.asciidoc
View File

@ -17,7 +17,10 @@ Shrinking works as follows:
* Then it hard-links segments from the source index into the target index. (If
the file system doesn't support hard-linking, then all segments are copied
into the new index, which is a much more time consuming process.)
into the new index, which is a much more time consuming process. Also if using
multiple data paths, shards on different data paths require a full copy of
segment files if they are not on the same disk since hardlinks don’t work across
disks)
* Finally, it recovers the target index as though it were a closed index which
had just been re-opened.