Yes, it happens on every message. I ran the zookeeper, server,
console-producer against --broker-list localhost:9092 --topic test, then shut
everything down and restarted the zookeeper and server and ran the
console-consumer --zookeeper localhost:2181 --topic test and both the server
console a
If this happens on every message, it indicates a problem. Could you wipe
out all ZK and Kafka data and try it again? If it still doesn't work, could
you try the latest revision in the 0.8 branch?
Thanks,
Jun
On Fri, Apr 5, 2013 at 8:50 AM, Withers, Robert wrote:
> Yes, it happens on every mess
I deleted all ZK and Kafka data and reran the ZK and one server. I got some
log traffic at this point. It looks like the server is elected Leader. The ZK
is on port 2181 and the server is on port 9092.
[2013-04-05 10:17:35,523] INFO 0 successfully elected as leader (kafka.server.Zo
okeeperLea
Hi,
I have an Eclipse java project, with the 2.9.1 scala jar
(scala-library-2.9.1.RC4.jar) in the build path, as well as the
kafka_2.8.0-0.8-SNAPSHOT.jar. I wrote the simple Producer example and try to
run it and it fails with a NoClassDefFoundError runtime exception. Here is my
code and the
We had something like this happen a few weeks ago. In our development
environment we are prototyping with 0.8. Since we're prototyping we
occasionally wipe our brokers and deploy the latest of 0.8. I never
completely verified but I think this may have happened in our case because
we renamed a topi
We're setting up a new kafka cluster with many brokers. How can we set a
topic partition count to be less than total # of brokers in the cluster.
The reason for this is we figure our cluster will have more sequential IO
and and thus significantly higher performance than a setup where there's 1
part
You should only include the 2.8 scala jar.
Thanks,
Jun
On Fri, Apr 5, 2013 at 9:41 AM, Withers, Robert wrote:
> Hi,
>
> I have an Eclipse java project, with the 2.9.1 scala jar
> (scala-library-2.9.1.RC4.jar) in the build path, as well as the
> kafka_2.8.0-0.8-SNAPSHOT.jar. I wrote the simple
The following is the problem. The broker fails to become the leader. Do you
know the revision of the code you are using so that we know the exact line
that's causing the problem?
Thanks,
Jun
[2013-04-05 10:21:09,660] ERROR Replica Manager on Broker 0: Error
processing le
aderAndISR request Name:
