data-tiers.asciidoc 1.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. // tag::cloud[]
  2. . Log in to the {ess-trial}[{ess} Console].
  3. . Add or select your deployment from the {ess} home page or the deployments
  4. page.
  5. . From your deployment menu, select **Edit deployment**.
  6. . To enable a data tier, click **Add capacity**.
  7. **Enable autoscaling**
  8. {cloud}/ec-autoscaling.html[Autoscaling] automatically adjusts your deployment's
  9. capacity to meet your storage needs. To enable autoscaling, select **Autoscale
  10. this deployment** on the **Edit deployment** page. Autoscaling is only available
  11. for {ess}.
  12. // end::cloud[]
  13. // tag::self-managed[]
  14. To assign a node to a data tier, add the respective <<node-roles,node role>> to
  15. the node's `elasticsearch.yml` file. Changing an existing node's roles requires
  16. a <<restart-cluster-rolling,rolling restart>>.
  17. [source,yaml]
  18. ----
  19. # Content tier
  20. node.roles: [ data_content ]
  21. # Hot tier
  22. node.roles: [ data_hot ]
  23. # Warm tier
  24. node.roles: [ data_warm ]
  25. # Cold tier
  26. node.roles: [ data_cold ]
  27. # Frozen tier
  28. node.roles: [ data_frozen ]
  29. ----
  30. We recommend you use dedicated nodes in the frozen tier. If needed, you can
  31. assign other nodes to more than one tier.
  32. [source,yaml]
  33. ----
  34. node.roles: [ data_content, data_hot, data_warm ]
  35. ----
  36. Assign your nodes any other roles needed for your cluster. For example, a small
  37. cluster may have nodes with multiple roles.
  38. [source,yaml]
  39. ----
  40. node.roles: [ master, ingest, ml, data_hot, transform ]
  41. ----
  42. // end::self-managed[]