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

Support single graphite instances outside of hashring #1

Open
jjneely opened this issue Jun 5, 2015 · 2 comments
Open

Support single graphite instances outside of hashring #1

jjneely opened this issue Jun 5, 2015 · 2 comments

Comments

@jjneely
Copy link
Owner

jjneely commented Jun 5, 2015

The client needs to support a daemon running on a single graphite host that is not part of a hashring. Goal here is to manage a single instance. Or multiple single instances.
@AlexAkulov
Copy link
Contributor

When will this feature appear?

@jjneely
Copy link
Owner Author

jjneely commented Jul 7, 2016

This is supported in a limited way now. Mostly my use case has been this: I removed a storage node from the cluster and I need to drain all the metrics on it. Or I want to pull all metrics off this rouge host into the Graphite cluster.

This can be done with the rebalance subcommand. Just give it the HOST:PORT of the buckyd daemon on the host that's not in the current hashring.

bucky rebalance -h <host-in-cluster:port> <external-host:port>

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

No branches or pull requests
2 participants
@jjneely @AlexAkulov