The documentation about it is all about coping with high load of audit processing. It also have a “main” instance, and secondaries ones processing only the audit queue.
In my situation, we use Service Control mainly for the Heartbeats and the Monitoring plugin. We also use Pulse to view failed messages. We disabled audits and we are not really interested in them.
We are trying to modify our architecture to reach high availability. We already setup the broker (rabbitmq) as a cluster for high availability, and are in the process of modifying our services to support multiple instances of each services.
But currently, the ServiceControl/ServiceMonitoring is only installed on one machine. I would like to have multiple instances so that if that machine shut down, it keeps being functional on the second one (mainly so that the heartbeat and monitoring queues doesn’t keep growing).
The configuration requires a specific queue names (SendHeartbeatTo/SendMetricDataToServiceControl), and the documentation linked above mention “Having multiple primary instances is discouraged.”, and to give a different names for the secondary instances.
So I guess this scenario is not supported yet?