One more thing ..
We have this configured as well.
systems.kafka.producer.metadata.broker.list=sprfargas102:6667,sprfargas103:6667
On Mon, Mar 30, 2015 at 5:08 PM, Shekar Tippur wrote:
> Hello,
>
> I realise this is a Kafka question. Since there are quite a few Kafka
> experts here and the ans
Hi Andrew,
The first thought I have is that, the container keeps failing due to some
exceptions. Could you check all the AM and containers run successfully? You
can see the logs in $HADOOP_Home/logs/userlogs
Thanks,
Fang, Yan
yanfang...@gmail.com
On Mon, Mar 30, 2015 at 4:05 PM, Andrew Sannier
Hello,
I realise this is a Kafka question. Since there are quite a few Kafka
experts here and the answer to this question can help Samza community as
well, bringing this question here.
We are testing Kafka redundancy (just 2 brokers for now).
We have increased replication factor to 2 servers (Bo
Hi -
Thanks in advance for your help.
I have been following this guide
http://samza.apache.org/learn/tutorials/0.8/run-in-multi-node-yarn.html trying
to prove that my samza cluster runs. I get as far as having a Running YARN
task, as the tutorial specifies, but this task doesn’t actually do an
+1
1. Validated hello-samza works with 0.9.0 Maven binaries.
2. Validated release-0.9.0-rc0 tag exists and has correct checksums.
3. Validated source release tarball builds, and has correct licenses
(bin/check-all.sh).
4. Validated source release tarball validates against Yan's PGP key.
5. Ran rol
+1
* Created and tested an sample job doing a join
* Build packages
* Couldn't get integration tests to work. It seemed like it was timing out
trying to download dependencies. I may have been having network issues
last night.
Cheers,
Roger
On Sun, Mar 29, 2015 at 9:09 PM, Jakob Homan wrote:
