Starting in Elasticsearch version 7.10, a new
node_roles field has been added to each Elasticsearch element in a deployment plan. The new
node_roles field is used in place of the original
node_types field when you enable a new feature such as autoscaling, or when you add a new warm and cold data tier.
This change might affect your index allocation and you need to take certain actions to ensure your index allocation and index lifecycle policies will continue to work as expected. See Migrate index allocation filters to node roles for instructions.
If you use the Deployment API to manage your deployment, you need to update your integration to support the new node_roles field. There are a few important things to note:
When migrating from
node_roles, it is not possible to go back to using
The Elasticsearch topology elements must either all use
node_typeor all use
node_rolesfield is supported only on Elasticsearch version 7.10 and above.
The deployment templates have been updated to also include other elements (for example,
topology_element_controller). These elements should also be sent when updating the deployment through the API.
If you manage your deployment through the UI, the deployment will automatically update to use the new
node_roles field when you enable autoscaling or add a warm or cold data tier.
If you use custom deployment templates, the templates need to be updated to support node_roles and autoscaling. Once that support has been added, deployments created using the custom template are enabled to use the autoscaling feature as well as hot, warm, cold, and frozen data tiers.
Intro to Kibana
ELK for Logs & Metrics