Hi, In a deployment, we use a CRX (TarPM) active/passive cluster composed of one master instance and one slave instance. We run background jobs on this deployment and we want to have them run on the CRX master only in order to guarantee no writes on the slave thus keeping the activate/passive scheme.
The way we currently do it is by checking in our background code, that the instance is the Sling leader and only run the code if the instance is the leader. This works only if the following holds at any time Sling leader == CRX master We experienced some cases where this seemed not to be the case. Should we expect the above mentioned mapping to be valid or should be find another way to enforce background services to only execute on the master ? We could use some CRX specific code for that, but our code would not become portable to other MK. Regards, Timothee
