It seems to work, but we're just starting to use the system. As I get more developers experimenting we'll see how it goes. There are still a lot of people out there not benefiting from AWS services like autoscaling groups and load balancers so it seems there isn't a lot of documention on using AWS for zookeeper clusters. I'm curious what other people are doing to dynamically change their config files when a zookeeper cluster needs to be scaled up. They just doing this all manually? Elastic is the future. So hence why these questions are coming up.
On Mon, May 4, 2015 at 6:55 AM, Andrew Medeiros <[email protected]> wrote: > Brian, > > I am under the same situation of not wanting to hardcore the zookeeper IPs > otherwise it makes autoscaling pretty impossible. Have you tried putting > your zookeeper cluster behind an ELB yet? If so what where your results? > Thank you! > > Cheers, > Andrew Medeiros > > — > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > On Thu, Apr 30, 2015 at 11:32 AM, Brian Fleming <[email protected]> > wrote: > >> I'm working in AWS. >> >> I have a load balancer in front of my zookeeper cluster. >> >> Can I use the load balancer DNS alias instead of entering the individual >> IPs in the config? This way I don't need to constantly change the IP >> addresses if they change. >> >> I guess if every operation to zookeeper is transactional, it should be >> fine, right? >> >> Thanks >> > >
