When you say "keeps getting below exception" I'm assuming that the error offset (206845418) keeps changing - right? We saw a similar issue in the past and it turned out to be due to a NIC issue - i.e., it negotiated at a low speed. So the replica fetcher couldn't keep up with the leader. i.e., while it caught up within the first segment the leader's log would roll (i.e., the segment would get deleted) and we would see the out of range error. Is this broker a follower for other partitions? Do those partitions show up in these error message?
On Fri, May 22, 2015 at 03:11:09PM +0800, tao xiao wrote: > Hi team, > > One of the brokers keeps getting below exception. > > [2015-05-21 23:56:52,687] ERROR [Replica Manager on Broker 15]: Error when > processing fetch request for partition [test1,0] offset 206845418 from > consumer with correlation id 93748260. Possible cause: Request for offset > 206845418 but we only have log segments in the range 207804287 to > 207804287. (kafka.server.ReplicaManager) > This is the follower broker of topic test1 and ISR of that topic has only 1 > broker left right now. Just wanted to know what cause this issue and how I > can prevent it? > > -- > Regards, > Tao
