A stale service is one that has been registered as a synchronization target, however, it has not responded to any attempt to synchronize data for a period of time greater than that defined in the consider-stale-hours parameter with which the source Access service was configured. Once a target service is deemed to be stale, the source service will not make any further attempts to synchronize data to it. To "revive" a stale service and resume synchronizing data you need to manually apply the Federation REST API endpoint described in Synchronize Data in Access Federation on the source service.
Once a target service is deemed to be stale, the source service will not make any further attempts to synchronize data to it. To revive a stale service and resume synchronizing data you can manually apply the Federation REST API endpoint described in Apply a REST API Endpoint on the Source Service to Invoke a Full Broadcast.
From Artifactory 7.77.3, you can configure Access Federation to automatically revive a stale service.
Set the property, federation.outbound.auto-full-sync-recovered-servers, as true in the Access Configuration YAML file to automatically recover a stale service. The default value is false.
Full synchronization might be a database heavy operation and can be performance intensive.
The property, federation.outbound.max-stored-events, decides the threshold number of events stored in the database. By default, the value is -1, which means that unlimited number of events are stored.
federation:
.
.
outbound:
.
.
max-stored-events: 100
auto-full-sync-recovered-servers: true