forcemerge.asciidoc 2.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. [[indices-forcemerge]]
  2. == Force Merge
  3. The force merge API allows to force merging of one or more indices through an
  4. API. The merge relates to the number of segments a Lucene index holds within
  5. each shard. The force merge operation allows to reduce the number of segments by
  6. merging them.
  7. This call will block until the merge is complete. If the http connection is
  8. lost, the request will continue in the background, and any new requests will
  9. block until the previous force merge is complete.
  10. WARNING: Force merge should only be called against *read-only indices*. Running
  11. force merge against a read-write index can cause very large segments to be produced
  12. (>5Gb per segment), and the merge policy will never consider it for merging again until
  13. it mostly consists of deleted docs. This can cause very large segments to remain in the shards.
  14. [source,js]
  15. --------------------------------------------------
  16. POST /twitter/_forcemerge
  17. --------------------------------------------------
  18. // CONSOLE
  19. // TEST[setup:twitter]
  20. [float]
  21. [[forcemerge-parameters]]
  22. === Request Parameters
  23. The force merge API accepts the following request parameters:
  24. [horizontal]
  25. `max_num_segments`:: The number of segments to merge to. To fully
  26. merge the index, set it to `1`. Defaults to simply checking if a
  27. merge needs to execute, and if so, executes it.
  28. `only_expunge_deletes`:: Should the merge process only expunge segments with
  29. deletes in it. In Lucene, a document is not deleted from a segment, just marked
  30. as deleted. During a merge process of segments, a new segment is created that
  31. does not have those deletes. This flag allows to only merge segments that have
  32. deletes. Defaults to `false`. Note that this won't override the
  33. `index.merge.policy.expunge_deletes_allowed` threshold.
  34. `flush`:: Should a flush be performed after the forced merge. Defaults to
  35. `true`.
  36. [source,js]
  37. --------------------------------------------------
  38. POST /kimchy/_forcemerge?only_expunge_deletes=false&max_num_segments=100&flush=true
  39. --------------------------------------------------
  40. // CONSOLE
  41. // TEST[s/^/PUT kimchy\n/]
  42. [float]
  43. [[forcemerge-multi-index]]
  44. === Multi Index
  45. The force merge API can be applied to more than one index with a single call, or
  46. even on `_all` the indices. Multi index operations are executed one shard at a
  47. time per node. Force merge makes the storage for the shard being merged
  48. temporarily increase, up to double its size in case `max_num_segments` is set
  49. to `1`, as all segments need to be rewritten into a new one.
  50. [source,js]
  51. --------------------------------------------------
  52. POST /kimchy,elasticsearch/_forcemerge
  53. POST /_forcemerge
  54. --------------------------------------------------
  55. // CONSOLE
  56. // TEST[s/^/PUT kimchy\nPUT elasticsearch\n/]