If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Switch to upstream graphite multi-instance configs and init scripts

NEW
Assigned to

Status

Infrastructure & Operations
Tools
--
enhancement
3 years ago
2 years ago

People

(Reporter: ericz, Assigned: ericz)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
Graphite used to not have built-in support for more than one instance but it appears to be much more capable now.  See if we can revert to a single config file and use the built-in init scripts and get rid of our customizations.
(Assignee)

Updated

3 years ago
Severity: normal → enhancement
(Assignee)

Comment 1

3 years ago
Created attachment 8508958 [details]
Combined carbon.conf

Attached a combined carbon.conf.
(Assignee)

Comment 2

3 years ago
Although for Ubuntu, these init scripts might be useful.  I like the number vs letter approach to naming cache and relay instances.  https://github.com/obfuscurity/graphite-scripts/tree/master/init.d

Comment 3

2 years ago
Eric,

I took a look at the existing init script and it seemed ok. Isn't obfuscurity script a customization? I don't understand..
(Assignee)

Comment 4

2 years ago
Yeah I think we can ignore obfuscurity's stuff but I do prefer his numeric instance naming to our current alphabetical naming.  The built-in carbon init script: https://github.com/graphite-project/carbon/blob/master/distro/redhat/init.d/carbon-cache should work fine with a single carbon.conf file.  It starts/stops all instances at once and doesn't allow for manipulating a single instance, but that's usually what we want to do so that's fine.
You need to log in before you can comment on or make changes to this bug.