Moving and scaling services

Content Platform for Cloud Scale Administration Guide

Version
2.6.x
File Size
1945 KB
Audience
anonymous
Part Number
MK-HCPCS008-10

You can change a service to run on more instances, fewer instances, or different instances.

You can change a service to run on:

  • Additional instances (for example, to improve 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, to retire the piece of hardware on which an instance is installed)

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 for distributing services

  • Monitor resource usage (CPU, RAM, disk) and services such as Prometheus regularly and adjust the scaling of services across instances as needed.
  • Ensure that there are enough instances that the cluster can still manage the volume and growth of objects if one or even two instances fail.
  • Distributing instances of product services onto master instances is discouraged. For more information refer to Best practices for system sizing and scaling.

Considerations

  • You cannot remove a service from an instance if doing so would cause or risk causing data loss.
  • Service relocations can take a long time to complete and can impact system performance while they are running.
  • Instance needs vary from service to service. Each service defines the minimum and maximum number of instances on which it can run.
Tip: Use the Available Instances option to make a floating service eligible to run on any instance in the system, including any new instances added in the future.