← Back to team overview

graphite-dev team mailing list archive

Re: [Question #101729]: Distributed database for Graphite

 

Question #101729 on Graphite changed:
https://answers.launchpad.net/graphite/+question/101729

    Status: Open => Answered

chrismd proposed the following answer:
Hi Steven, sorry for the delay in getting back to you it's been a crazy
weekend.

The good news is I think Graphite can help you. You can setup as many
graphite installations on different servers as you need, each with its
own carbon-cache (the storage backend you send your data to) and webapp
instance. You can then configure the webapps to share data with one
another completely transparently by defining a CLUSTER_SERVERS list in
your local_settings.py. Multiple remote data centers should work fine,
that's what I'm deploying myself in the next few weeks. The latency
shouldn't stop you from doing anything but it can affect the
responsiveness of browsing the metric hierarchy as well as how long it
takes to render graphs since those things involve sharing data.

You generally don't need to manage whisper databases yourself, carbon-
cache does that for you. If you want to do custom rendering you can
still get at the raw data through the webapp.

As for the volume of data I think you could get by with as many or as
few graphite servers as you'd like. My current production system is a 2
node cluster with each server handling 1 datapoint per minute for
approximately 300,000 metrics.

Hope that helps. If you do decide to try graphite out feel free to ask
questions, I'd like to know if you run into any problems.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.