-
Notifications
You must be signed in to change notification settings - Fork 140
Kafka_0_9_support #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kafka_0_9_support #168
Conversation
I got a Scheduler Test Failure when I tried to build this: oad https://repo1.maven.org/maven2/org/scala-lang/scala-reflect/2.10.6/scala-reflect-2.10.6.jar ly.stealth.mesos.kafka.SchedulerTest > syncBrokers FAILED ly.stealth.mesos.kafka.SchedulerTest > launchTask FAILED ly.stealth.mesos.kafka.SchedulerTest > acceptOffer FAILED ly.stealth.mesos.kafka.SchedulerTest > newTask FAILED ly.stealth.mesos.kafka.CliTest > connection_refused FAILED |
Could you please send a zip-ed test reports. It will contain a stack trace. Also could you please build with |
…dded .ipr files to gitignore
I have found the problem why the test were failing, I have created a pull request that fixes the test execution on the Kafka_0_9_support branch. The problem that the version was missing in the temporary .tgz files, a placeholder version number is now added. |
Merged fix of @Hylke1982 . |
stepped through upgrade procedure looks good, after stopping old scheduler and starting new one
|
Nice work! |
@joestein are the steps you listed required to upgrade to kafka 0.9 and 0.9.4 of the framework? I'm currently on 0.9.2.0 of the framework. |
Hey @mindscratch If you are running 0.9.4.0 scheduler and want to stick to running Kafka 0.8.X brokers that is fine too. To upgrade the scheduler stop your scheduler and start the new one (however you are scheduling HA). What makes the broker Kafka 0.8.X vs 0.9.X is the Kafka binary you download that is sitting in the directory with the jar when you start the scheduler. In the steps above before I had two directories one for 0.9.3.0 mesosKafka and kafka 0.8.2.2. That scheduler turned off and started 0.9.4.0 mesosKafka. At that point all the tasks/broker where still exactly like they were before 0.8.2.2 brokers still running happily along. When the stop/update/start occured for each task/broker when it started the new kafka_2.11-0.9.0.0.tgz is what the scheduler gave back as the URI and made available for download to the executer when it restarted back up
|
@joestein the upgrade steps you documented previously worked great, thanks! |
Pushed PR with changes required for 0.9 support.
Joe, please review&eval&merge when will have time.