Would it be possible to take a "group commit" approach rather than configuring a delay. I.e. all changes that come in at once while another operation is occurring automatically get batched. This can sometimes be nicer and more automatic than another tunable parameter...
-Jay On Fri, Aug 7, 2015 at 9:29 AM, Jiangjie Qin <j...@linkedin.com.invalid> wrote: > Hi, > > I just created KIP-29 to add a new configuration of IsrPropagateIntervalMs > to KafkaConfig. The motivation is to batch and throttle the ISR propagation > in cases where large amount of ISR change occurs such as a broker gets > bounced or failed. Otherwise it might overwhelm the controller. > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-29+-+Add+an+IsrPropagateIntervalMs+configuration+to+KafkaConfig > > This is a config addition and is backward compatible. > > Thoughts? > > Thanks, > > Jiangjie (Becket) Qin >
