Federated repository sync works by syncing the metadata for artifacts first. The source instance will push the metadata for artifacts to the target instance. Due to this, you will see the artifact in the UI and it will be resolvable.
The corresponding binary on the other hand is pulled on the target instance from the source instance. However, the binary for the artifact is not immediately pulled over when the metadata is pushed. When the metadata is pushed, a reference to the corresponding binary is added to a table called “binary_tasks” in the target instance’s database.
If the artifact is requested on the target instance and the binary isn’t pulled over to the target instance yet, it will be pulled over on demand. Otherwise, there is a job on the target instance that periodically queries its “binaries_tasks” table to pull over the binaries from the source instance.
There may be a need to tune the pull process of binaries on the target instance.
The corresponding binary on the other hand is pulled on the target instance from the source instance. However, the binary for the artifact is not immediately pulled over when the metadata is pushed. When the metadata is pushed, a reference to the corresponding binary is added to a table called “binary_tasks” in the target instance’s database.
If the artifact is requested on the target instance and the binary isn’t pulled over to the target instance yet, it will be pulled over on demand. Otherwise, there is a job on the target instance that periodically queries its “binaries_tasks” table to pull over the binaries from the source instance.
There may be a need to tune the pull process of binaries on the target instance.