Hi,
yes, I'm seeing the errors on the crashed broker.
My controller.log file only contains the following:
[2014-01-03 09:41:01,794] INFO [ControllerEpochListener on 1]: Initialized
controller epoch to 11 and zk version 10
(kafka.controller.ControllerEpochListener)
[2014-01-03 09:41:01,812] INFO
How many replicas do you have on that topic? What's the output of list
topic?
Thanks,
Jun
On Mon, Jan 6, 2014 at 1:45 AM, Vincent Rischmann wrote:
> Hi,
>
> yes, I'm seeing the errors on the crashed broker.
>
> My controller.log file only contains the following:
>
> [2014-01-03 09:41:01,794] I
Thanks Neha.
Menka
On Sun, Jan 5, 2014 at 3:13 PM, Neha Narkhede wrote:
> That's right.
> On Jan 5, 2014 2:45 PM, "Menka" wrote:
>
> > http://upload.wikimedia.org/wikipedia/commons/f/f7/Apache_kafka.png
> >
> > Please help me confirm.
> >
> > Thanks,
> > Menka
> >
> >
> >
> > --
> > Blog: http
Hi,
I'm working through some examples and I'm having issues with activating more
than one server. I'm running on an AWS instance on an Amazon Linux AMI. The
single node to single broker worked like a charm, yet every time I configure my
second server it throws an error and shutdown's my first
in server.properties you also need to change the kafka port if you are
running everything on one machine
# The port the socket server listens on
port=9092
There is a great writeup on running multi broker on single machine
http://www.michael-noll.com/blog/2013/03/13/running-a-multi-broker-apache-k
Balaji,
Which Kafka version are you using?
On Sat, Jan 4, 2014 at 9:56 AM, Seshadri, Balaji
wrote:
> Consumer offset checker shows its connected to
> consumer(account-access-hadoop-consumer_tm1mwdpl03-1383065261413-15d3cb41-0)
> but that consumer is not started,what could be reason its showing
Hi, all ~
There are 3 zookepers and one broker, Kafka 0.7.2.
I got some temporary problems in zk cluster enviornment, but, any zk
processes didn't go down.
A broker got zk session timeout message, then got zk disconnected and
expired message.
After 10 secs, the broker reconnected to the zk with n
That issue has been uncovered
https://issues.apache.org/jira/browse/KAFKA-778 as occurring when the
producer sees 0 partitions for a topic.
A quick fix might be to change over your topic name to something new so it
gets auto created again and disband the old topic name.
Longer term fix would be t
