You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

High Availability Archiva

Questions

What options do we have for clustering Archiva instances?

Can it work with multiple instances using the same filesystem?

Yes, but keep the index files (and probably the database) separate.

What things can be shared, and what must remain separate?

  • Repository filesystem can be shared
  • Lucene indexes should not be shared (too much file locking to make it work)

How can upgrades be handled to minimize downtime?

Example configuration

Two servers running Archiva with a virtual IP device in front. Shared filesystem. Everyone uses
a single url that goes to the VIP, which monitors port 8080 on the servers to see which one is available. Right now it's done as
failover to a hot standby, but we eventually want it load balanced, and will add more repository servers as necessary. We've also
switched to MySQL for the user database, to take advantage of its replication and admin features.

Brief Explanation of the Repository Index

Please see http://www.nabble.com/Location-of-index-files-in-1.0--tf3901605s177.html#a11064078

  • No labels