graphite-dev team mailing list archive

[Daniel Schauenberg <question208946@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

Daniel Schauenberg proposed the following answer:
Hi,

this is probably best handled on the carbon side with a loadbalancer. For
StatsD to switch to the slave, you have to update the config file which is then
reloaded. That takes a considerable amount of time, which is not really in the
realm of uninterrupted failover anymore.

Cheers,
Daniel

On Tue, Sep 18, 2012 at 09:25:57PM -0000, Orion Fillmore wrote:
>New question #208946 on Graphite:
>https://answers.launchpad.net/graphite/+question/208946
>
>Hello,
>
>I am setting up a carbon cluster with the main purpose of fail-safe.  I read the documentation about carbon-relay and federated storage, but my question is (and this might be something I need to be posting on a stated forum) this:
>
>Assume my "master" carbon server crashes, how will statsd know to send to the data over tcp to my "slave" servers?   Is this something that is handled on the statsd end or the carbon end?  Should I just use a load balancer?  Is there a recommended methodology for this?  Perhaps these are basic questions, but I am new to graphite!
>
>Any help or pointers in the right direction is greatly appreciated!
>
>-Fillmore
>
>--
>You received this question notification because you are a member of
>graphite-dev, which is an answer contact for Graphite.
>
>_______________________________________________
>Mailing list: https://launchpad.net/~graphite-dev
>Post to     : graphite-dev@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~graphite-dev
>More help   : https://help.launchpad.net/ListHelp

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