Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High availability setup #108

Open
clauded opened this issue May 21, 2020 · 1 comment
Open

High availability setup #108

clauded opened this issue May 21, 2020 · 1 comment

Comments

@clauded
Copy link

clauded commented May 21, 2020

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?
@ThrawnCA
Copy link
Collaborator

ThrawnCA commented Oct 4, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants