Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Support multiple APIs for the same data center #173

Closed
amdprophet opened this issue Oct 27, 2014 · 6 comments
Closed

Support multiple APIs for the same data center #173

amdprophet opened this issue Oct 27, 2014 · 6 comments
Labels

Comments

@amdprophet
Copy link
Member

Redundancy is a good thing. We should investigate implementing support for multiple APIs within the same data center so that Uchiwa can failover to another API & support rudimentary load balancing.

@palourde
Copy link
Contributor

Wouldn't be easier to move the APIs behind a load balancer? I'm assuming that in case of an HA Sensu setup, a load balancer would already be in place for RabbitMQ, for example.

@amdprophet
Copy link
Member Author

Load balancers are still a single point of failure. @portertech implemented support for multiple RabbitMQ instances in 0.15.0.beta-1. If we decide to support this feature we can probably use Sensu's implementation as a reference.

@palourde
Copy link
Contributor

How I see it: we'll probably need to add an another property in the Sensu object of the JSON configuration file. Then, the URL property (which combine the Ssl, Host and Port properties) used by the backend would need to be replaced by a slice, in which we inject the single or multiple addresses (I'll assume that both APIs are configured with the same user/pass). Finally, whenever a call is made to the APIs, we iterate on the URL slice until we have a positive response.

It's not impossible but it would definitively require a good amount of work!

@chiriaev
Copy link

chiriaev commented Apr 1, 2015

Guys, Hi. On a slightly different not, I would add distinction between GET and PUT/POST/DELETE API calls and let the administrator decide which API instance to query. It would help reading, for example, from an API connected to a local REDIS slave, and writing to a "master" on a different server. (i.e.: across the Atlantic perhaps)

Regards, Andrei

@palourde
Copy link
Contributor

Added with 0.11.0

@palourde
Copy link
Contributor

Wrong issue, my bad!

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

No branches or pull requests

3 participants