Managing services
This section describes how you can reconfigure, restart, and otherwise manage the services running on your system.
Moving and scaling services
You can change a service to run on:
- Additional instances (for example, if you need improved service performance and availability).
- Fewer instances (for example, to free up resources on an instance for running other services).
- A different set of instances (for example, if you are retiring the piece of hardware on which an instance is installed).
For information on:
- Individual services and the number of instances they should run on, see Service list.
- Monitoring service relocation operations, see Monitoring service operations.
Moving and scaling floating services
For floating services, instead of specifying the specific instances on which the service runs, you can specify a pool of eligible instances, any of which can run the service.
Moving and scaling services with multiple types
When moving or scaling a service that has multiple types, you can simultaneously configure separate rebalancing for each type.
Best practices
- Avoid running multiple services with high service unit costs together on the same instance.
- On master instances, avoid running any services besides those classified as System services.
Considerations
- Instance requirements vary from service to service. Each service defines the minimum and maximum number of instances on which it can run.
- You cannot remove a service from an instance if doing so causes or risks causing data loss.
- Service relocation might take a long time to complete and can impact system performance.
Relocating services
Procedure
Select Services.
The Services page opens, displaying the services and system services.Select the service that you want to scale or move.
Configuration information for the service is displayed.Click Scale, and if the service has more than one type, select the instance type that you want to scale.
- The next step depends on whether the service is floating or persistent (non-floating).
If the service is a floating service, you are presented with options for configuring an instance pool. For example:
In the box Service Instances, specify the number of instances on which the service should be running at any time.
Configure the instance pool:
- For the service to run on any instance in the system, select All Available Instances.
With this option, the service can be restarted on any instance in the instance pool, including instances that were added to the system after the service was configured.
- For the service to run on a specific set of instances, clear All Available Instances. Then:
- To remove an instance from the pool, select it from the list Instance Pool, on the left, and then click Remove Instances.
- To add an instance to the pool, select it from the list Available Instances, on the right, and then click Add Instances.
- For the service to run on any instance in the system, select All Available Instances.
If the service is a persistent (non-floating) service, you are presented with options for selecting the specific instances that the service should run on. Do one or both of these, then click Next:
- To remove the service from the instances it's currently on, select one or more instances from the list Selected Instances, on the left, and then click Remove Instances.
- To add the service to other instances, select one or more instances from the list Available Instances, on the right, and then click Add Instances.
Click Update.
The Processes page opens, and the Service Operations tab displays the progress of the service update as "Running." When the update finishes, the service shows "Complete."
Next steps
Related CLI commands
updateServiceConfig
Related REST API methods
POST /services/configure
You can get help on specific REST API methods for the Admin App at REST API - Admin.
Configuring service settings
Select the Services window.
Select the service you want to configure.
On the Configuration tab, configure the service.
Click Update.
Related CLI commands
updateServiceConfig
Related REST API methods
POST /services/configure
You can get help on specific REST API methods for the Admin App at REST API - Admin.
Adding volumes to services
Click the Services window.
Select a service.
Click Configuration.
On the Volumes tab, click the Manage Volumes link for an instance of the service. A window appears that lists the different types of volumes that the service instance supports.
In the Volume Names field, type the name of the applicable Docker volume that you want the service instance to use.
Repeat the previous step for each Docker volume you want to add to the service instance.
Click Save.
Repeat steps 4 through 7 for each instance of the service you want to configure.
Click Update.
Related CLI commands
updateServiceConfig
Related REST API methods
POST /services/configure
You can get help on specific REST API methods for the Admin App at REST API - Admin.
Repairing services
If a service becomes slow, unresponsive, or shows a status of Failed, you can repair it.
Repairing a service stops and restarts the service on each instance on which it's running.
To repair a service:
Procedure
Click the Services window.
Select the service you want to repair.
Click Repair.
The Processes window opens, displaying a progress bar for the repair process.
Splitting Index shards
Admin App users can take advantage of Solr’s shard splitting API to increase the number of shards on their index after creation.
The Desired Index Shard Count config property allows users flexibility with sizing their clusters. Shard splitting separates the largest shard in two shards, each containing half of the data of the original. After splitting the shards, the index retains identical data and query responses.
The scheduled solr-maintenance service action helps the Index service handle these requests, running every three minutes. If a shard split operation is currently in progress, the action does nothing. If no shard split operations are in progress (or if a shard split operation has completed), the action searches for pending shard split operations. After they're discovered, the operations are run and any inactive shards are deleted along with those leftover from the previously completed operations.
To split your shards using this feature:
Procedure
Open the Admin App.
Select the Services tab.
Select the Index service.
Select the Configuration tab.
Navigate to the config group for your selected shard.
In the Desired Index Shard Count field, enter the new shard value.
At the top of the window, click Update.
Results
A WARNING level alert appears notifying the user that a shard split is in progress. The alert clears when the operation is completed.
- Changes to this value on larger indexes needs additional time before taking effect.
- This value can only be changed if the Index Protection Level is below 3 and cannot be decreased at a later time.