Skip to content
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

Issue #167 #207

Closed
wants to merge 71 commits into from
Closed

Issue #167 #207

wants to merge 71 commits into from

Conversation

nukemberg
Copy link

This is a patch/pull request for 0.9.x, not master. resolves issue 167

mleinart and others added 30 commits August 13, 2012 23:42
Fixed up file and directory handling in response to issues graphite-project#17 and graphite-project#18

Conflicts:
	lib/carbon/writer.py
…xisting to prevent log spam when new metrics are created in existing directory trees

Cleaned up whitespace in log.py
Stop log spam, clean up some more formatting.
Token bucket based rate limiting
deque instead of list for datapoint storage inside cache
removed locks and need for locks during threaded interaction between writer and cache
MetricCache.pop now automatically returns the metric with the largest number of cached datapoints
No more cache sorts!
Configurable cache writer strategies
defaultdict for the main cache datastructure (backwards compatible with 2.4 even!)
some other stuff I've probably forgotten!
…uency

carbon.conf: Add [aggregator] WRITE_BACK_FREQUENCY
Refactor cache to not require locks
Add different write ordering behaviors
Use token buckets for write rate limiting
Add FORWARD_ALL parameter to aggregator
Refactor hashing for clarity
improve CH routing performance when replfactor=1

Re-merge due to loss in a big merge commit
The MAX value is an integer, but was being divided by 60, and so
was producing an integer result.  Therefore, if MAX was < 60,
the result is 0 and no new metrics are created after the initial
MAX is hit.  If MAX is >= 60, new metrics will be created, though
not at exactly the rate that would be expected.

The TokenBucket expects floating point values, so force the
division to be floating point.

Fixes issue graphite-project#55.
Treat MAX_CREATES_PER_MINUTE as a float.
bitprophet and others added 22 commits February 19, 2013 21:31
Fix misreporting cache size/queues metrics
otherwise they goes as "nan" in the whisper files
…or datapoints of

a set of metrics, which gives much better performance than single request per metric.
Add new type of cache query - 'cache-query-bulk'
Updated example config to demonstrate new options
Added Configurable files for aggregation and rewrite rules
Fixes compat with twisted 13.2.0 by removing dead code.
Fixed broken aggregation rules file config
@pcn
Copy link

pcn commented Jan 27, 2014

Can you close this out, and re-apply your patch on top of the 0.9.x branch without all of the intermediate commits that you've added to this PR?

Thanks!

@nukemberg
Copy link
Author

i've not added intermediate commits, github is showing you the diff against
master.
i've rebased on 0.9.x. is it better now?

On Mon, Jan 27, 2014 at 5:19 PM, Peter N notifications@github.com wrote:

Can you close this out, and re-apply your patch on top of the 0.9.x branch
without all of the intermediate commits that you've added to this PR?

Thanks!


Reply to this email directly or view it on GitHubhttps://github.com//pull/207#issuecomment-33375872
.

@obfuscurity
Copy link
Member

Sorry, this PR is a total mess. You rebased off 0.9.x but you're pulling against master. The subject is completely absent of any context. I don't mean to be harsh, but it really is hard to follow what you're attempting to fix. Would you mind starting over with a clean PR?

@nukemberg nukemberg deleted the issues/167 branch August 14, 2014 19:00
@nukemberg nukemberg restored the issues/167 branch August 14, 2014 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet