Assign Roles to Runners

Assigning roles might be required after you install Elastic Cloud Enterprise on hosts to make sure the new hosts (runners) can be used for their intended purpose and to remove roles from the initial host to implement a recommended ECE installation. Similarly, if you need more processing capacity for Elasticsearch nodes in your deployment, change the role of a new runner to allocator to add its capacity to your installation.

These steps describe how to assign roles from the Cloud UI. For automation purposes, assigning roles with a token you generate is preferred.

Each Elastic Cloud Enterprise runner can take on several roles:

allocator
Allocates the available computing resources to Elasticsearch nodes or Kibana instances. In larger installations, a majority of the machines will be allocators.
coordinator
Serves as a distributed coordination system and resource scheduler.
proxy
Manages communication between a user and an Elasticsearch or Kibana instance.
director
Manages the ZooKeeper datastore. This role is typically shared with the coordinator role. In production deployments it can be separated from a coordinator.

Each role is associated with a set of Docker containers that provide the specific functionality.

There are some additional roles shown in the Cloud UI, such as the beats-runner and services-forwarder roles, that are required by Elastic Cloud Enterprise and that you cannot modify.

To assign roles to runners:

  1. Log into the Cloud UI.
  2. From the Platform menu, select Runners.

    The roles for each runner are shown.

  3. To update the roles, click the runner IP address and then select Update roles from the menu.
  4. Select the role assignments for that runner and click Update roles.

Elastic Cloud Enterprise automatically starts managing the node in its new role and makes it available for use.

To learn more about how you should assign roles, see deployment recommendations.