Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAA9QSJLAp5C4amJkgRVTpFhbWt1jtZOvx3dTFfQOKpBG_t38sQ@mail.gmail.com>
References: 
 <CAJDuW=BoCOESP6XZ_cjNvrSmsWtH4XX3ohK5GJ2rPiqr2HOFQA@mail.gmail.com>
	<CAA9QSJLAp5C4amJkgRVTpFhbWt1jtZOvx3dTFfQOKpBG_t38sQ@mail.gmail.com>
Date: Wed, 13 Jan 2016 20:39:13 -0500
Message-ID: 
 <CAA9QSJ+A-P5CrOVc5Af+68ZTdwpU341RM=jDcuPpOgb_=p5OnA@mail.gmail.com>
Subject: Re: [VOTE] KIP-41: Consumer Max Records
From: Gwen Shapira <gwen@confluent.io>
To: dev@kafka.apache.org
Content-Type: multipart/alternative; boundary=001a113e57689a6b530529415afc

--001a113e57689a6b530529415afc
Content-Type: text/plain; charset=UTF-8

Also, great job on the KIP, Jason.

I love the solution you found and I love how well you explained it in the
KIP.

On Wed, Jan 13, 2016 at 8:38 PM, Gwen Shapira <gwen@confluent.io> wrote:

> +1 (binding)
>
> On Wed, Jan 13, 2016 at 6:18 PM, Jason Gustafson <jason@confluent.io>
> wrote:
>
>> Hi All,
>>
>> I'd like to open up the vote on KIP-41. This KIP adds a new consumer
>> configuration option "max.poll.records" which sets an upper bound on the
>> number of records returned in a call to poll(). This gives users a way to
>> limit message processing time to avoid unexpected rebalancing. This change
>> is backwards compatible with the default implementing the current
>> behavior.
>>
>> Here's a link to the KIP wiki:
>>
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-41%3A+KafkaConsumer+Max+Records
>>
>> Thanks,
>> Jason
>>
>
>

--001a113e57689a6b530529415afc--