Story #3474: Maintain consistency across CN hazelcast backing datastores
Create custom merge policy to support managing data/information inconsistency
The current merge policy in our Hazelcast clusters will add all entries to the cluster that creates a superset of entries found across members. This may cause conflicts, especially when the same object has different content (like a system metadata record with differing replica entries and statuses). Create a new merge policy class that compares content for entries in hzSystemMetadata, and re-sync entries across nodes, prioritizing entries where the dateSysMetadataModified date is the newest and serialVersion is the highest.
Possible extension of existing merge policy which currently ensure the number of records in each backing datastore in the cluster is consistent. Extend to ensure the information contained in each datastore is consistent.