Is this issue re-producible? Can you try start up a new cluster, then kill
one broker and check list-topics before and afterwards to see if this issue
still exist?
On Tue, Jan 21, 2014 at 10:07 PM, Xiao Bo wrote:
> I also tried changing the broker id to a new id: 5 and still got many many
> sim
I also tried changing the broker id to a new id: 5 and still got many many
similar warnings and no data generated in log.dir.
[2014-01-21 18:00:00,923] WARN [KafkaApi-5] Fetch request with correlation
id 1528423082 from client ReplicaFetcherThread-0-1 on partition [co,9]
failed due to Partition [c
Before the broker 1 died, the replicas and leaders were even distribued on
the 5 node cluster. And the previous replication factor were 3.
2014/1/22 Guozhang Wang
> Do you still have the results of list-topics before broker 1 is dead? From
> the current result it seems the replication factor i
Do you still have the results of list-topics before broker 1 is dead? From
the current result it seems the replication factor is 2 not 3.
Guozhang
On Tue, Jan 21, 2014 at 9:26 PM, Xiao Bo wrote:
> Yes, the topic name is countinfo, Maybe in the log it generates a short
> name automatically.
>
Yes, the topic name is countinfo, Maybe in the log it generates a short
name automatically.
2014/1/22 Guozhang Wang
> Hello,
>
> What is your topic name? From the log it seems to be "co", but from
> list-topic it is "countinfo".
>
> Guozhang
>
>
> On Tue, Jan 21, 2014 at 8:24 PM, Xiao Bo wrot
Thanks for reply. Yes, the broker id is the same.
We have tried just restarting the broker, but after 1 day there were still
no partition files generated in the log.dir and by list-topic I could not
see broker-1 back. Any other way can I add it back ?
As I said in last mail, the topic seems having
Hello,
What is your topic name? From the log it seems to be "co", but from
list-topic it is "countinfo".
Guozhang
On Tue, Jan 21, 2014 at 8:24 PM, Xiao Bo wrote:
> Hi guys and jun,
>
> We have a problem when adding a breakdown broker back to the cluster. Hope
> you guys have some solution fo
Hi guys and jun,
We have a problem when adding a breakdown broker back to the cluster. Hope
you guys have some solution for it.
A cluster of 5 brokers(id=0~4) of kafka 0.8.0 was running for log
aggregation . Because of some issues of the disk, a broker(id=1) was down.
We spent one week to repl
