You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're planning to deploy our CKAN setup with high availability (two CKAN servers, one db container, one solr container and one redis container). We would like to have xloader highly available as well.
Is there a problem if we install the extension on both CKAN servers?
Is there any possible conflicts doing so?
Any special configuration to do?
The text was updated successfully, but these errors were encountered:
HA XLoader is certainly possible. However, there is an increased risk of slowdowns and database transaction deadlocks when datasets have a high number of resources and different XLoader instances compete over them.
We have a setup that puts XLoader on its own server(s), and no special configuration is needed; it just needs the CKAN configuration file, and access to the database and Redis queue, just like CKAN would.
We're planning to deploy our CKAN setup with high availability (two CKAN servers, one db container, one solr container and one redis container). We would like to have xloader highly available as well.
The text was updated successfully, but these errors were encountered: