Using a Spring distributed cache to prevent watchdogs working on the same ADVISED cm handles during model sync, since we don't have an in-between state from ADVISED to READY.

Eg

Watchdog A wakes up, works on Cm-Handle-1 which has state of ADVISED and stores this in memory

Watchdog B wakes up, attempts to work on Cm-Handle-1, which still has a state of ADVISED, but is being worked on by Watchdog A, so this then moves on to Cm-Handle-2

Potential Implementations:

https://reflectoring.io/spring-boot-hazelcast/

https://www.nexsoftsys.com/articles/distributed-caching-in-java-microservices-using-redis-cluster.html

A/C:

• Run the CLM job to verify the dependency.
  https://jenkins.onap.org/view/CLM/job/cps-maven-clm-master/99/
  Shorthand : run-clm

 - Test : Something with the logging / 2 instances waking up at the same time. (Module Sync)

 - Test : Something with the logging / 2 instances waking up at the same time.(Data Sync)

Open Issues:

• Check for the latest version.*