anyone help?
> 在 2016年3月29日，18:57，jinhong lu <lujinho...@gmail.com> 写道：
>
>
>
> Hi, I found this log in my server.log.
>
> The offset of replication is larger than leader's, so the replication data
> will delete, and then copy the the data from leader.
> But when copying, the cluster is very slow, some storm topology fail due to
> no response from kafka.
>
> So:
> (1)How to avoid this problem occurs?
> (2)when replication is copying, how to slow down the replication rate?
>
> here is the log:
>
> [2016-03-29 18:24:59,349] INFO Scheduling log segment 3773408933 for log
> g17-4 for deletion. (kafka.log.Log)
> [2016-03-29 18:24:59,349] INFO Scheduling log segment 3778380412 for log
> g17-4 for deletion. (kafka.log.Log)
> [2016-03-29 18:24:59,403] WARN [ReplicaFetcherThread-3-4], Replica 2 for
> partition [g17,4] reset its fetch offset from 3501121050 to current leader
> 4's start offset 3501121050 (kafka.server.ReplicaFetcherThread)
> [2016-03-29 18:24:59,403] ERROR [ReplicaFetcherThread-3-4], Current offset
> 3781428103 for partition [g17,4] out of range; reset offset to 3501121050
> (kafka.server.ReplicaFetcherThread)
> [2016-03-29 18:25:27,816] INFO Rolled new log segment for 'g17-12' in 1 ms.
> (kafka.log.Log)
> [2016-03-29 18:25:35,548] INFO Rolled new log segment for 'g18-10' in 2 ms.
> (kafka.log.Log)
> [2016-03-29 18:25:35,707] INFO Partition [g18,10] on broker 2: Shrinking ISR
> for partition [g18,10] from 2,4 to 2 (kafka.cluster.Partition)
> [2016-03-29 18:25:36,042] INFO Partition [g18,10] on broker 2: Expanding ISR
> for partition [g18,10] from 2 to 2,4 (kaka.cluster.Partition)
>
>
> BR//lujinhong
