-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.9.12 nodaemon backport #144
Conversation
Not even a single comment on this? The Internet is filled with people trying to figure out how to deal with the carbon daemons not being able to be reasonably started and stopped using modern process control. Having a |
+1 from me. I like this. It just needs to back out the twisted version peg so that the merge can happen. |
+1 |
This is a copy/paste from my comment in #191: I spent some time yesterday researching exactly how to properly control Graphite carbon-cache, as it sits in the v0.9.12 tag, using Upstart and have posted a working config here: https://gist.github.com/dbeckham/8057390 Using the info from carbon/conf.py, carbon/util.py, and the Internet, I've created a I'll be rolling this out in our Puppet environment shortly, but If anyone has any issues with it, or suggestions for making it better, please comment on the gist. |
👍 |
this should go in. 🤘 |
@jib Would you mind rebasing against |
0.9.x nodaemon backport (rebase of #144 to 0.9.x branch)
We run all our carbon daemons under supervisor, and not having this patch is a tremendous performance penalty as it forces us to run in --debug mode, so we backported this fix from master.
Please consider integrating it in the 0.9.x branch so we (and others) can keep up with 0.9.x releases.