I remember being on a call with product management about a year ago, in which the PM mentioned a (sort-of) tombstone age in relation to x-site synchronization.
That is to say, a period of time (or number of changes to the DB) during which a secondary site cluster member can be re-synced, but after which a re-sync is not possible and therefore require a cluster restart.
Use Case:
CA PAM 3.2.4
Multi Site Cluster
One node in a secondary site falls out of sync, all other nodes in all sites are synced.
Is there a tombstone age that, once passed, would require a cluster-restart to get all nodes back in sync? Or can that secondary node stay out of sync for a very long time and be re-synced with a simple "RE-SYNC SITE MEMBER" ?
Thanks in advance.
------------------------------
Services Architect
HCL Technologies Ltd
------------------------------