Hi, Twitter recently open source libcrunch. https://blog.twitter.com/2013/libcrunch-and-crush-maps. It uses the crush algorithm to do the placement. It also takes care of rack aware placement. I have looked at the code in detail. It will be nice to compare the difference between what we have in Helix v/s this implementation. Here is the code https://github.com/twitter/libcrunch/tree/master/src/main/java/com/twitter/crunch
I think we should probably have a new module(helix-rebalancers) where we plugin multiple rebalancers. Thoughts? thanks, Kishore G
