+ user
On Thu, Mar 6, 2014 at 5:24 AM, Leonard Kramer < [email protected]> wrote: > Hi Mr. Kishore, > > my name is Leonard Kramer and I've found your mail-address in the Apache > Helix mailing list. I'm currently evaluating Apache Helix for the > cluster-management of ZooKeeper itself. The ultimate goal is to create an > autonomous zookeeper-service with its own migration-strategies and self > repair functions. > > For the monitoring and reaction to outages of nodes I want to use Apache > Helix, because it already uses ZooKeeper as its primary coordination & > data-store. In the mailing-list you have answered a thread for the > differences between norbert and helix and mentioned that "Failure: When a > node fails, you have multiple options [...] #3 Start a new node and assign > the partitions to that new node. [...] #3 feature is work in progress and > is possible if the deployment system is flexible and allows starting up > process dynamically". > While studying Helix I couldn't find any more information regarding this > feature. All I could find was the blog post "http://engineering.linkedin. > com/cluster-management/auto-scaling-apache-helix-and-apache-yarn", which > I think is too complex for my specific use-case. > > Can you please provide me with more information regarding the self repair > of a helix cluster? Is the helix-controller capable of invoking logic for > starting additional nodes? My plan is to use Jclouds in addition to the > cloud-controller and start a new node when the helix-controller notices a > node's failure. Is this possible? > > Thank you for your help and have nice day. > Greetings from Germany > > Leo >
