{"action":"created","issue":{"url":"https://api.github.com/repos/facebook/mcrouter/issues/51","labels_url":"https://api.github.com/repos/facebook/mcrouter/issues/51/labels{/name}","comments_url":"https://api.github.com/repos/facebook/mcrouter/issues/51/comments","events_url":"https://api.github.com/repos/facebook/mcrouter/issues/51/events","html_url":"https://github.com/facebook/mcrouter/issues/51","id":83733321,"number":51,"title":"Question about ch3/furc hashing algorithm","user":{"login":"gotascii","id":419,"avatar_url":"https://avatars.githubusercontent.com/u/419?v=3","gravatar_id":"","url":"https://api.github.com/users/gotascii","html_url":"https://github.com/gotascii","followers_url":"https://api.github.com/users/gotascii/followers","following_url":"https://api.github.com/users/gotascii/following{/other_user}","gists_url":"https://api.github.com/users/gotascii/gists{/gist_id}","starred_url":"https://api.github.com/users/gotascii/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gotascii/subscriptions","organizations_url":"https://api.github.com/users/gotascii/orgs","repos_url":"https://api.github.com/users/gotascii/repos","events_url":"https://api.github.com/users/gotascii/events{/privacy}","received_events_url":"https://api.github.com/users/gotascii/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-01T22:57:14Z","updated_at":"2015-06-01T23:25:20Z","closed_at":null,"body":"Hi there,\r\n\r\nI've noticed that when adding a box to the end of the list of servers in a PoolRoute using ch3 that it behaves as one would expect, in accordance with [this comment in hash.h](https://github.com/facebook/mcrouter/blob/master/mcrouter/lib/fbi/hash.h#L21-L45). However, recently we needed to remove a box about 2/3 of the way up in the list of servers. Coming from a hash ring implementation that was using [ketama](http://www.metabrew.com/article/libketama-consistent-hashing-algo-memcached-clients) we were greeted with quite a surprise when we rolled out the new config that removed the offending host. About 2/3 of the cluster was cold :/ What's the best way to handle removing various failing hosts from the config? Is this just something that shouldn't be happening all that often and TKO tracking + FailOverRoutes should be good enough to hold over while a bad host is reprovisioned? Any chance that Ketama could be added as a hash option?\r\n\r\nThanks!\r\nJustin Marney"},"comment":{"url":"https://api.github.com/repos/facebook/mcrouter/issues/comments/107745658","html_url":"https://github.com/facebook/mcrouter/issues/51#issuecomment-107745658","issue_url":"https://api.github.com/repos/facebook/mcrouter/issues/51","id":107745658,"user":{"login":"gotascii","id":419,"avatar_url":"https://avatars.githubusercontent.com/u/419?v=3","gravatar_id":"","url":"https://api.github.com/users/gotascii","html_url":"https://github.com/gotascii","followers_url":"https://api.github.com/users/gotascii/followers","following_url":"https://api.github.com/users/gotascii/following{/other_user}","gists_url":"https://api.github.com/users/gotascii/gists{/gist_id}","starred_url":"https://api.github.com/users/gotascii/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gotascii/subscriptions","organizations_url":"https://api.github.com/users/gotascii/orgs","repos_url":"https://api.github.com/users/gotascii/repos","events_url":"https://api.github.com/users/gotascii/events{/privacy}","received_events_url":"https://api.github.com/users/gotascii/received_events","type":"User","site_admin":false},"created_at":"2015-06-01T23:25:20Z","updated_at":"2015-06-01T23:25:20Z","body":"Sounds good, thanks for the clarification! If we end up taking a crack at adding ketama we'll send along a PR."}}