- In certain cases, maintaining near real-time synchronization of all artifact events (create, update, delete) among Federation members may not be possible to maintain near real-time synchronization of all artifact events due to:
- Short-term networking issues between the JPDs
- Artifactory upgrades
- User-initiated synchronization pause
- Other similar scenarios.
- If synchronization continues to fail after reaching the maximum number of retry events, event sync is paused, and the Federation transitions into an error state.
- To recover the Federation, one approach is to perform a full sync. However, this can be time-consuming, especially if the Federated repositories contain a large number of artifacts, effectively restarting the Federation.
- Starting with release 7.71.1, Artifactory introduces an auto-healing mechanism. This mechanism regularly checks Federated repositories for exhausted queues (queues that have exceeded the maximum number of attempts to send events to other Federation members). If such queues are detected, the mechanism resets the failed events automatically and attempts to sync with the target mirror again. See Federation Recovery and Auto-Healing for more information.