Thanks Liam Clarke-Hutchinson for inputs.
Yes, the case that i described is very rare as it is expected *like you
mentioned already *the replica failures are transient and eventually caught
up once they are back . And the kind of infrastructure we have today, this
could eventually be supported by
Hi Nag,
In my experience running Kafka in production for 6 years, so long as the
number of replicas (and the leader is one of those replicas) in the insync
replica set (ISR) is greater than the min.insync.replica setting, the
partition leader will accept writes, and customers can read those
Hey Nag Y,
I’m not exactly sure if reducing the replication factor while a broker is
down would release the messages to be consumed (or at least not on all
partitions) for the simple fact that it might just remove the last replica
in the list which might not mach your unreachable broker.
Thanks D C. Thanks a lot . That is quite a detailed explanation.
If I understand correctly, ( ignoring the case where producers
create transactions) - since the replica is down and never comes , the high
watermark CANNOT advance and the consumer CAN NOT read the messages which
were sent after the
The short answer is : yes, a consumer can only consume messages up to the
High Watermark.
The long answer is not exactly, for the following reasons:
At the partition level you have 3 major offsets that are important to the
health of the partition and accessibility from the consumer pov:
LeO (log
As I understand it, the consumer can only read "committed" messages - which
I believe, if we look at internals of it, committed messages are nothing
but messages which are upto the high watermark.
*The high watermark is the offset of the last message that was successfully
copied to all of the
