For distributing services
Each service has an associated service unit cost. These costs indicate how computationally expensive one service is to run compared to another. You can use these costs as a guide for how to distribute services across the instances in your system.
Recommendations
•Avoid running multiple services with high service unit costs together on the same instance.
Ideally, each of these services should run by itself on an instance:
oDatabase
oIndex
•On master instances, avoid running any services besides those classified as System services.
•To utilize your instances evenly, try to deploy a comparable number of service units on each instance. For more information, see Service units.
•Moving or scaling services can cause document failures during a workflow task. Before moving or scaling a service, you should either pause all running workflow tasks or wait for them to complete.
Related topics
For information on:
•The services and their costs, see Service list
•Configuring where a service runs, see Moving and scaling services
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 Hitachi Vantara Corporation. All rights reserved.