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.

Sign up for GitHub

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

Jump to bottom

When configured Query node is unavailable, queries fail #2

Open
johann8384 opened this issue Mar 26, 2016 · 1 comment
Open

When configured Query node is unavailable, queries fail #2

johann8384 opened this issue Mar 26, 2016 · 1 comment
Labels
feature request

Comments

@johann8384
Copy link
Contributor

No description provided.

@johann8384
Copy link
Contributor Author

Splicer should be able to failover to another configured query node at random, it may be better to use a service discovery method now that OpenTSDB can support this.

https://github.com/inst-tech/opentsdb-discoveryplugins

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johann8384