some trouble with the replica.lag.time.max.ms configuration

[xiang chen <it...@gmail.com>]

I cannot understand the mean of the following configuration:

replica.lag.time.max.ms <https://kafka.apache.org/documentation/#brokerconfigs_replica.lag.time.max.ms>
If a follower hasn't sent any fetch requests or hasn't consumed up to the leaders log end offset for at least this time, the leader will remove the follower from isr.

The official site mentioned the “consumed up to the leaders log end offset” but the confluent.io explain the caught up which refers to the high watermark of leader. So what is the configuration real means?

I look forward to hearing from you.



best wishes！

Attach: 

https://developer.confluent.io/courses/architecture/data-replication/
Kafka Data Replication Protocol: A Complete Guide
developer.confluent.io