{"action":"opened","issue":{"url":"https://api.github.com/repos/twitter/twemproxy/issues/337","labels_url":"https://api.github.com/repos/twitter/twemproxy/issues/337/labels{/name}","comments_url":"https://api.github.com/repos/twitter/twemproxy/issues/337/comments","events_url":"https://api.github.com/repos/twitter/twemproxy/issues/337/events","html_url":"https://github.com/twitter/twemproxy/issues/337","id":63860126,"number":337,"title":"Hashing Algorithms Sending everything to Different Nodes than Before","user":{"login":"NickMeves","id":4123100,"avatar_url":"https://avatars.githubusercontent.com/u/4123100?v=3","gravatar_id":"","url":"https://api.github.com/users/NickMeves","html_url":"https://github.com/NickMeves","followers_url":"https://api.github.com/users/NickMeves/followers","following_url":"https://api.github.com/users/NickMeves/following{/other_user}","gists_url":"https://api.github.com/users/NickMeves/gists{/gist_id}","starred_url":"https://api.github.com/users/NickMeves/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NickMeves/subscriptions","organizations_url":"https://api.github.com/users/NickMeves/orgs","repos_url":"https://api.github.com/users/NickMeves/repos","events_url":"https://api.github.com/users/NickMeves/events{/privacy}","received_events_url":"https://api.github.com/users/NickMeves/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-23T23:52:22Z","updated_at":"2015-03-23T23:52:22Z","closed_at":null,"body":"Using fnv1a_64 with modula.\r\n\r\n5 days ago we had a network outage on our switch/router (unannounced maintance, yay!) for 15ish minutes.\r\n\r\nSince networking has come back up, Nutcracker is hashing all keys (or subsets of the keys in the hash tag) to different nodes.  If before key foo always went to node1, now it is always going to node2.\r\n\r\nI have tried restarting the cluster, realigning which backend nodes are master/slave, recompiling nutcracker -- all keys all still hashing to the new nodes, rather than the previous proper nodes.  This is using named nodes in the nutcracker conf generated by redis-mgr.\r\n\r\nAny ideas on how to get hashing to go to back to how it was before? Or do I need to aof-replay everything and just accept the new hashing that is happening?\r\n\r\nI'm still perplexed how every key is all of the sudden hashing to new nodes."}}