Oh please ignore my last reply.
I find if leaderReplica.highWatermark.messageOffset >= requiredOffset , this
can ensure all replicas’ leo in curInSyncReplicas is >= the requiredOffset.
> 在 2016年9月23日，下午3:39，Kafka 写道：
>
> OK, the example before is not enough to exposure problem.
> What will ha
OK, the example before is not enough to exposure problem.
What will happen to the situation under the numAcks is 1，and
curInSyncReplica.size >= minIsr，but in fact the replica in curInSyncReplica
only have one replica has caught up to leader，
and this replica is the leader replica itself，this is n
In order to satisfy a produce response, there are two conditions:
A. The leader's high watermark should be higher than the requiredOffset
(max offset in that produce request of that partition)
B. The number of in sync replica is greater than min.isr.
The ultimate goal here is to make sure at least
@wangguozhang，could you give me some advices.
> 在 2016年9月22日，下午6:56，Kafka 写道：
>
> Hi all,
> in terms of topic， we create a topic with 6 partition，and each with 3
> replicas.
>in terms of producer，when we send message with ack -1 using sync
> interface.
> in terms of
Hi all,
in terms of topic， we create a topic with 6 partition，and each with 3
replicas.
in terms of producer，when we send message with ack -1 using sync
interface.
in terms of brokers，we set min.insync.replicas to 2.
after we review the kafka broker’s code，we know that w
