graphite-dev team mailing list archive

[Mark Lin <question59255@xxxxxxxxxxxxxxxxxxxxx>]

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

Mark Lin posted a new comment:
Sorry for being lame, so what do we have in graphite today as far as
multiple backend goes?

This is my understanding:

It works now by connecting multiple hosts via clustered filesystem, so
they are writing to the same location.  When the webapp needs the graph,
it reads off that file system and cache the data locally.

Let's say we don't run clustered file system and metrics comes in via
round robin fashion into multiple backend.  Would graphite be able to
query for data from every servers in CARBONLINK_HOSTS and aggregate the
data together?  I looked at carbon-cache.py, but don't know if
"cache.get(query,[])" only looked at cached data or also local files.

And a few more questions, hope you don't mind, regarding MEMCACHE_HOSTS
and REMOTE_RENDERING.  If we use multiple entries in MEMCACHE_HOSTS,
would webapp just do the hashing and spread cache data across listed
memcache servers?  And what do we need to install for server to be used
in REMOTE_RENDERING?  Just graphite?  The comment mentioned that it's
useful when we can share storage mount, so I assume the server receiving
the request will fetch the data and pass it to rendering host?


Thanks for your time,
Mark

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