settings.asciidoc 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879
  1. [float]
  2. [[breaking_80_settings_changes]]
  3. === Settings changes
  4. [float]
  5. [[search-remote-settings-removed]]
  6. ==== The `search.remote` settings have been removed
  7. In 6.5 these settings were deprecated in favor of `cluster.remote`. In 7.x we
  8. provided automatic upgrading of these settings to their `cluster.remote`
  9. counterparts. In 8.0.0, these settings have been removed. Elasticsearch will
  10. refuse to start if you have these settings in your configuration or cluster
  11. state.
  12. [float]
  13. [[remove-pidfile]]
  14. ==== `pidfile` setting is replaced by `node.pidfile`
  15. To ensure that all settings are in a proper namespace, the `pidfile` setting was
  16. previously deprecated in version 7.4.0 of Elasticsearch, and is removed in
  17. version 8.0.0. Instead, use `node.pidfile`.
  18. [float]
  19. [[remove-processors]]
  20. ==== `processors` setting is replaced by `node.processors`
  21. To ensure that all settings are in a proper namespace, the `processors` setting
  22. was previously deprecated in version 7.4.0 of Elasticsearch, and is removed in
  23. version 8.0.0. Instead, use `node.processors`.
  24. [float]
  25. ==== `node.processors` can no longer exceed the available number of processors
  26. Previously it was possible to set the number of processors used to set the
  27. default sizes for the thread pools to be more than the number of available
  28. processors. As this leads to more context switches and more threads but without
  29. an increase in the number of physical CPUs on which to schedule these additional
  30. threads, the `node.processors` setting is now bounded by the number of available
  31. processors.
  32. [float]
  33. ==== `cluster.remote.connect` is removed
  34. In Elasticsearch 7.7.0, the setting `cluster.remote.connect` was deprecated in
  35. favor of setting `node.remote_cluster_client`. In Elasticsearch 8.0.0, the
  36. setting `cluster.remote.connect` is removed.
  37. [float]
  38. ==== `node.local_storage` is removed
  39. In Elasticsearch 7.8.0, the setting `node.local_storage` was deprecated and
  40. beginning in Elasticsearch 8.0.0 all nodes will require local storage. Therefore,
  41. the `node.local_storage` setting has been removed.
  42. [float]
  43. ==== `auth.password` for HTTP monitoring is removed
  44. In Elasticsearch 7.7.0, the setting `xpack.monitoring.exporters.<exporterName>.auth.password`
  45. was deprecated in favor of setting `xpack.monitoring.exporters.<exporterName>.auth.secure_password`.
  46. In Elasticsearch 8.0.0, the setting `xpack.monitoring.exporters.<exporterName>.auth.password` is
  47. removed.
  48. [float]
  49. ==== Option to disable basic license features is deprecated
  50. In Elasticsearch 7.8.0, the following settings have been deprecated:
  51. * `xpack.enrich.enabled`
  52. * `xpack.flattened.enabled`
  53. * `xpack.ilm.enabled`
  54. * `xpack.monitoring.enabled`
  55. * `xpack.rollup.enabled`
  56. * `xpack.slm.enabled`
  57. * `xpack.sql.enabled`
  58. * `xpack.transform.enabled`
  59. * `xpack.vectors.enabled`
  60. In future releases, it will not be possible to disable the APIs for Enrichment,
  61. Flattened mappings, ILM, Monitoring, Rollup, SLM, SQL, Transforms, and Vectors.