I see. Storage configuration is global per Artifactory instance and cannot
be changed per repo.
The default is to store artifacts on the file-system and metadata in
DB. With databases, such as Oracle, that are doing efficient blob handling
you can have the binaries in the database, with the main
You can achieve content-based active/active by using sync-replication. This
requires some setting up to do, but allows any artifact deployed to one
server to be resolvable from the other server. With a load balancer in the
front for reads, clients can read from any server.
Writes need to be made
Is there any benefit to setting up two Artifactory instances - one for the
ISO repository storage and another for the smaller artifacts - or is that
overkill? (I suppose it would depend on the size of the ISO repository?)
At the moment I have just done a basic install on Ubuntu. Plan on moving it
Hi Yoav,
sounds interresting, thanks again.
Do you know about some references or preferred/recommended implementations
for this content-based sync replication (except for the replication feature
within Pro ) ?
--
View this message in context:
On Fri, Dec 9, 2011 at 1:42 PM, Peter Sellars psell...@gmail.com wrote:
Is there any benefit to setting up two Artifactory instances - one for the
ISO repository storage and another for the smaller artifacts - or is that
overkill? (I suppose it would depend on the size of the ISO repository?)
Anybody ever seen this one?
Our builds are getting a 500 error trying to get a snapshot artifact from the
repo. I've confirmed that it IS there.
2011-12-09 09:24:26,083 [pool-1-thread-21] [INFO ]
(o.a.r.i.IntegrationCleanerInterceptor:240) - Removed old unique snapshot
No, I was referring to the rsync-like replication feature of Artiafctory
Pro.
On Fri, Dec 9, 2011 at 3:51 PM, vdalan alain.eh.vanda...@gmail.com wrote:
Hi Yoav,
sounds interresting, thanks again.
Do you know about some references or preferred/recommended implementations
for this
