-
Notifications
You must be signed in to change notification settings - Fork 21
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
Is there a plans to merge jump branch to the master? #8
Comments
Are you looking to use that with carbon-c-relay's jump-fnv1a hashing algorithm? IIRC, that's what I was trying to imitate here. But being that I've never been able to push a hashring change in my current cluster this hasn't been merged. |
Yes. We are indeed trying to use it with carbon-c-relay's jump-fnv1a as it gives us more equal distribution of metrics between hosts. |
The fact that Graphite just does multiple destinations rather than true replication has been a big reason why I've not done more work on replication factor > 1. There's no real redundancy / data safety that adds. I'll take a look at getting that merged in. |
Hello! |
Hi. Yes, we currently using it. |
Ah, so you using a build from jump tree and it works, right? Cool, thanks! |
Nah, can't build it: |
Ah, of course - all imports are pointed to master version. So, the only way to build it - fork into the own repo, rename jump branch to master and change imports. Meh. Will test it and will try to properly merge it to master. |
This is in progress on my end.... |
This is merged. I'm sure there are a bug or three that I've forgotten about. |
@jjneely I think this breaks the 'standard' carbon hash implementation because the |
I'm sure there are some bugs here... Do have an error case to reproduce? I plan to be spending some more time on this in the coming weeks, I just unblocked myself from another issue this evening. |
@jjneely So I could be totally misunderstanding how everything works but this is what I did: |
I did an exactly same thing in my branch - deniszh/buckytools@ad89e74 - remove '+1' in ring length comparison. Still not understand how it should work with it. |
Good to know.... |
No description provided.
The text was updated successfully, but these errors were encountered: