- Elastic Cloud Enterprise - Elastic Cloud on your Infrastructure: other versions:
- What Is Elastic Cloud Enterprise?
- Getting Started
- Configuring Your Installation
- Securing Your Installation
- Monitoring Your Installation
- Administering Your Installation
- Administering Clusters
- Use Cases
- Troubleshooting
- API Reference
- Clusters - Elasticsearch - CRUD
- Clusters - Elasticsearch - CRUD - Configuration
- Clusters - Elasticsearch - Commands
- Clusters - Kibana - CRUD
- Clusters - Kibana - CRUD - Configuration
- Clusters - Kibana - Commands
- Platform
- Platform - Allocators
- Platform - Configuration - Security
- Platform - Configuration - TLS
- Platform - Repository - CRUD
- Stack - CRUD
- Definitions
AllocatedInstanceStatus
AllocatorCapacity
AllocatorCapacityMemory
AllocatorHealthStatus
AllocatorInformation2
AllocatorMoveRequest
AllocatorOverview
AllocatorZoneInformation
BasicFailedReply
BasicFailedReplyElement
ClusterCredentials
ClusterCrudResponse
ClusterInstanceDiskInfo
ClusterInstanceInfo
ClusterInstanceMemoryInfo
ClusterMetadataInfo
ClusterPlanStepInfo
ClusterPlanStepLogMessageInfo
ClusterTopologyInfo
CreateElasticsearchClusterRequest
CreateKibanaClusterRequest
ElasticsearchClusterInfo
ElasticsearchClusterPlan
ElasticsearchClusterPlanInfo
ElasticsearchClusterPlansInfo
ElasticsearchClusterRole
ElasticsearchClusterSecurityInfo
ElasticsearchClusterSettings
ElasticsearchClusterTopologyElement
ElasticsearchClusterUser
ElasticsearchClustersInfo
ElasticsearchConfiguration
ElasticsearchHttpUserSettings
ElasticsearchInfo
ElasticsearchMasterElement
ElasticsearchMasterInfo
ElasticsearchMonitoringInfo
ElasticsearchNodeType
ElasticsearchPlanControlConfiguration
ElasticsearchReplicaElement
ElasticsearchScriptTypeSettings
ElasticsearchScriptingUserSettings
ElasticsearchShardElement
ElasticsearchShardsInfo
ElasticsearchSystemSettings
ElasticsearchUserBundle
ElasticsearchUserPlugin
EmptyResponse
EnrollmentTokenRequest
GrowShrinkStrategyConfig
Hyperlink
InstanceMoveRequest
JSON
KibanaClusterInfo
KibanaClusterPlan
KibanaClusterPlanInfo
KibanaClusterPlansInfo
KibanaClusterTopologyElement
KibanaClustersInfo
KibanaConfiguration
KibanaPlanControlConfiguration
KibanaSubClusterInfo
KibanaSystemSettings
ListEnrollmentTokenElement
ListEnrollmentTokenReply
ManagedMonitoringSettings
ManagedSnapshotSettings
PlanStrategy
PlatformInfo
PlatformServiceImageInfo
PlatformServiceInfo
RepositoryConfig
RepositoryConfigs
RequestEnrollmentTokenReply
RestoreSnapshotApiConfiguration
RestoreSnapshotConfiguration
RestoreSnapshotRepoConfiguration
RollingStrategyConfig
SnapshotRepositoryConfiguration
SnapshotStatusInfo
StackVersionArchiveProcessingError
StackVersionArchiveProcessingResult
StackVersionConfig
StackVersionConfigPost
StackVersionConfigs
StackVersionElasticsearchConfig
StackVersionKibanaConfig
StackVersionTemplateFileHash
StackVersionTemplateInfo
TargetElasticsearchCluster
TiebreakerTopologyElement
TlsPublicCertChain
TransientElasticsearchPlanConfiguration
TransientKibanaPlanConfiguration
- Script Reference
- Release Notes
- About This Product
It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Assign Roles to Runners
editAssign Roles to Runners
editAssigning 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 cluster deployment. Similarly, if you need more processing capacity for Elasticsearch nodes in your cluster, 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 or Kibana clusters. 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.
Once the director
role is assigned to a runner, the Zookeeper service starts on that host. The Zookeeper service continues even after the director role is removed from the runner. Therefore, if you remove the director
role from any host that has ever had it, we highly recommend also deleting the runner and re-installing it.
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:
- Log into the Cloud UI.
- Go to Platform and select a Elastic Cloud Enterprise installation. The roles for each runner are shown.
- To update the roles, select a specific runner and then select Update roles.
- Let the user interface guide you through updating the node 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.