When configuring repository replication in Artifactory, the Include/Exclude Patterns fields enable fine-grained control over which artifacts get replicated. However, certain large-scale use cases can lead to unexpected issues if those patterns become very large.
Known Limitation
Replication job definitions internally store metadata (such as job parameters and pattern definitions) in database tables.
When the combined include/exclude pattern list is exceptionally large, it may exceed internal storage constraints and result in job failures or unexpected behavior.
Best Practices
Prefer replication for ongoing synchronization, not for very large one-time migrations.
For large one-time migrations, consider using dedicated migration tools instead of live replication.
Keep include/exclude patterns as concise and specific as possible.
Avoid replicating “everything and then deleting” when pushing to external or untrusted targets, as this can expose internal or sensitive content.
Monitor the total size (length and count) of your pattern definitions to avoid reaching internal limits.