It seems that somehow the follower lost its highwatermark checkpoint file.
Can you share the steps to reproduce this along with the Kafka versions you
are using?
On Mon, Dec 22, 2014 at 4:17 PM, Sa Li wrote:
> I have three nodes: 100, 101, and 102
>
> When I restart all of them, seems now everyt
I have three nodes: 100, 101, and 102
When I restart all of them, seems now everything is ok, but I would like to
paste the error messages I got from server.log from each node, see if you
can help to understand what is the problem.
on node 100
[2014-12-23 00:04:39,401] ERROR [KafkaApi-100] Error
Hello, Neha
This is the error from server.log
[2014-12-22 23:53:25,663] WARN [KafkaApi-100] Fetch request with
correlation id 1227732 from client ReplicaFetcherThread-0-100 on partition
[perf_producer_p8_test,1] failed due to Leader not local for partition
[perf_producer_p8_test,1] on broker 100
I restart the kafka server, it is the same thing, sometime nothing listed
on ISR, leader, I checked the state-change log
[2014-12-22 23:46:38,164] TRACE Broker 100 cached leader info
(LeaderAndIsrInfo:(Leader:101,ISR:101,102,100,LeaderEpoch:0,ControllerEpoch:4),ReplicationFactor:3),AllReplicas:101
There is possibly some error in your broker logs. Can you check if you see
any and send it around?
On Mon, Dec 22, 2014 at 2:46 PM, Sa Li wrote:
> Hi, All
>
> I created a topic with 3 replications and 6 partitions, but when I check
> this topic, seems there is no leader and isr were set for this
Hi, All
I created a topic with 3 replications and 6 partitions, but when I check
this topic, seems there is no leader and isr were set for this topic, see
bin/kafka-topics.sh --create --zookeeper 10.100.98.100:2181
--replication-factor 3 --partitions 6 --topic perf_producer_p6_test
SLF4J: Class p
