Hi kafka community and developers,
in our current state of development of a new internal software we at a
state, where we could roll out a first alpha-version of our product. Our
production team has doubts in productional deployment and maintenance of
the kafka instances.
Therefore they requested
Hello Kafka wizards!
Congratulations on achieving beta on the 0.8 release! We've been waiting too
long for it!
I have two questions regarding the high level consumer in 0.8 used from scala:
I found this example on how to use the high level consumer from Java:
https://cwiki.apache.org/confluence
We've upgraded our ZK installation to 3.4.5 (by using the apt package from
CDH) about a month ago and have been running it since without much issue.
In our case, the only problem is that our previous installation of ZK had
unlimited client connections (maxClientCnxns=0) and the vanilla CDH
install
I wanted to send this out because we saw this in some testing we were doing and
wanted to advise the community of something to watch for in 0.8 HA support.
We have a two machine cluster with replication factor 2. We took one machine
offline and re-formatted the disk. We re-installed the Kafka
Hi, Bob,
Thanks for reporting this. Yes, this is the current behavior when all
brokers fail. Whichever broker comes back first becomes the new leader and
is the source of truth. This increases availability. However, previously
committed data can be lost. This is what we call unclean leader electio
Some of our tools use a consumer in Scala. You can take a look at
ConsoleConsumer or MirrorMaker.
Thanks,
Jun
On Fri, Jun 21, 2013 at 1:16 PM, Florin Trofin wrote:
> Hello Kafka wizards!
>
> Congratulations on achieving beta on the 0.8 release! We've been waiting
> too long for it!
> I have t
Hi, Everyone,
We will be having our user group meeting next Thursday evening at LinkedIn
in Mountain View. The following is the venue and the tentative agenda.
http://www.meetup.com/http-kafka-apache-org/events/125887332/
Hope to see many of you there!
Jun
