[ https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208515#comment-14208515 ]
Ewen Cheslack-Postava commented on KAFKA-1173: ---------------------------------------------- [~joestein] To be honest, I'm not too surprised something is coming up with the EC2 support. In theory it should be simple, but VPCs introduce a bunch of variables, and testing is tricky since some defaults depend on the age of your account since that affects whether you have EC2 classic support. I ran through a test with a VPC and found some issues. I updated the patch, including some additional info in the README since setting up under a VPC requires slight differences. My testing so far has been in EC2-Classic since that's the default for my account. I also put this VPC in a different region to make sure that worked. Finally, I've noticed that the default parallel provisioning seems to work fine until the very end, when it sometimes seems to hang. I couldn't easily track down the cause, so I updated the readme to use --no-parallel when using EC2. Not ideal, but it works reliably until we can find a better fix. Hopefully those fixes will clear up the issue you're seeing. > Using Vagrant to get up and running with Apache Kafka > ----------------------------------------------------- > > Key: KAFKA-1173 > URL: https://issues.apache.org/jira/browse/KAFKA-1173 > Project: Kafka > Issue Type: Improvement > Reporter: Joe Stein > Assignee: Ewen Cheslack-Postava > Attachments: KAFKA-1173.patch, KAFKA-1173_2013-12-07_12:07:55.patch, > KAFKA-1173_2014-11-11_13:50:55.patch, KAFKA-1173_2014-11-12_11:32:09.patch > > > Vagrant has been getting a lot of pickup in the tech communities. I have > found it very useful for development and testing and working with a few > clients now using it to help virtualize their environments in repeatable ways. > Using Vagrant to get up and running. > For 0.8.0 I have a patch on github https://github.com/stealthly/kafka > 1) Install Vagrant [http://www.vagrantup.com/](http://www.vagrantup.com/) > 2) Install Virtual Box > [https://www.virtualbox.org/](https://www.virtualbox.org/) > In the main kafka folder > 1) ./sbt update > 2) ./sbt package > 3) ./sbt assembly-package-dependency > 4) vagrant up > once this is done > * Zookeeper will be running 192.168.50.5 > * Broker 1 on 192.168.50.10 > * Broker 2 on 192.168.50.20 > * Broker 3 on 192.168.50.30 > When you are all up and running you will be back at a command brompt. > If you want you can login to the machines using vagrant shh <machineName> but > you don't need to. > You can access the brokers and zookeeper by their IP > e.g. > bin/kafka-console-producer.sh --broker-list > 192.168.50.10:9092,192.168.50.20:9092,192.168.50.30:9092 --topic sandbox > bin/kafka-console-consumer.sh --zookeeper 192.168.50.5:2181 --topic sandbox > --from-beginning -- This message was sent by Atlassian JIRA (v6.3.4#6332)