Story #975: Refactor to support synchronization across multiple MNs
Messaging from CN to listen for Node Service changes
If a new node is created or a synchronization schedule changed on existing node, the synchronization process will need to re-evaluate which CN is responsible for triggering Jobs. Also, will need to reload the distributed hash.
Modified cn_rest_service's NodeController to use hazelcast client when registering a new Membernode.