index-apis.asciidoc 2.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051
  1. [[breaking_50_index_apis]]
  2. === Index APIs changes
  3. ==== Closing / deleting indices while running snapshot
  4. In previous versions of Elasticsearch, closing or deleting an index during a
  5. full snapshot would make the snapshot fail. In 5.0, the close/delete index
  6. request will fail instead. The behavior for partial snapshots remains
  7. unchanged: Closing or deleting an index during a partial snapshot is still
  8. possible. The snapshot result is then marked as partial.
  9. ==== Warmers
  10. Thanks to several changes like doc values by default and disk-based norms,
  11. warmers are no longer useful. As a consequence, warmers and the warmer API
  12. have been removed: it is no longer possible to register queries that will run
  13. before a new IndexSearcher is published.
  14. Don't worry if you have warmers defined on your indices, they will simply be
  15. ignored when upgrading to 5.0.
  16. ==== System CPU stats
  17. The recent CPU usage (as a percent) has been added to the OS stats
  18. reported under the node stats API and the cat nodes API. The breaking
  19. change here is that there is a new object in the `os` object in the node
  20. stats response. This object is called `cpu` and includes `percent` and
  21. `load_average` as fields. This moves the `load_average` field that was
  22. previously a top-level field in the `os` object to the `cpu` object. The
  23. format of the `load_average` field has changed to an object with fields
  24. `1m`, `5m`, and `15m` representing the one-minute, five-minute and
  25. fifteen-minute loads respectively. If any of these fields are not present,
  26. it indicates that the corresponding value is not available.
  27. In the cat nodes API response, the `cpu` field is output by default. The
  28. previous `load` field has been removed and is replaced by `load_1m`,
  29. `load_5m`, and `load_15m` which represent the one-minute, five-minute
  30. and fifteen-minute loads respectively. The field will be null if the
  31. corresponding value is not available.
  32. Finally, the API for `org.elasticsearch.monitor.os.OsStats` has
  33. changed. The `getLoadAverage` method has been removed. The value for
  34. this can now be obtained from `OsStats.Cpu#getLoadAverage` but it is no
  35. longer a double and is instead an object encapsulating the one-minute,
  36. five-minute and fifteen-minute load averages. Additionally, the recent
  37. CPU usage can be obtained from `OsStats.Cpu#getPercent`.
  38. ==== Suggest stats
  39. Suggest stats exposed through `suggest` in indices stats has been merged
  40. with `search` stats. `suggest` stats is exposed as part of `search` stats.