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
It's been a mystery for me to understand the Cluster mechanism for graphite.
I've tried to spin up multiple carbon-caches in one instance, which failed.
And also tried to having two instances running graphite stack with relay replicating metrics, configured local_settings.py to include CLUSTER config with endpoints listening on port 80, that succeed, but causing unsustainable delay for querying.
My question is, is there a better way to put up a cluster for an overloaded single node graphite? How does it scale ?
Thanks for your help.
David
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
HI ,
It's been a mystery for me to understand the Cluster mechanism for graphite.
I've tried to spin up multiple carbon-caches in one instance, which failed.
And also tried to having two instances running graphite stack with relay replicating metrics, configured local_settings.py to include CLUSTER config with endpoints listening on port 80, that succeed, but causing unsustainable delay for querying.
My question is, is there a better way to put up a cluster for an overloaded single node graphite? How does it scale ?
Thanks for your help.
David
The text was updated successfully, but these errors were encountered: