Just to keep everyone posted. The following is a summary of what's being
discussed in the KIP hangout today.

KIP-4 (admin commands):
* Gwen is uploading a patch in KAFKA-1927 (refactoring requests) so that we
can get unblocked of adding new requests.
* We will combine DescribeTopic and TopicMetadata in the future.
* We will leave the admin requests async for now.
* We will not add a VerifyReassignPartitionRequest for now. We can do that
later when we improve the verification process.
* We need to discuss a bit more on how to expose the controller info to the
client.
* Andrii will send out more details on the KIP thread.

KIP-15 (close):
* If close() or close with a non-zero timeout is called from the send
thread, we will log it as an error.
* Jiangjie will follow up on the KIP thread.

KIP-13 (quota):
* Need a separate discussion on whether to use the new metrics package on
the broker on the mailing list.
* There are a few other details being discuss and Aditya will follow up on
the KIP thread.

Thanks,

Jun


On Fri, Mar 20, 2015 at 2:44 PM, Jun Rao <j...@confluent.io> wrote:

> Hi, Everyone,
>
> We plan to have a KIP discussion on Google hangout on Mar 24 at 11am PST.
> If you are interested in participating and have not already received a
> calendar invitation, please let me know. The following is the agenda.
>
> KIP-4 (admin commands): 10 mins
> * status of KAFKA-1927 (refactoring requests). which blocks this KIP
> * status of KAFKA-1634 (improve OffsetCommitRequest), which blocks
> KAFKA-1927
> * any remaining issues for discussion
>
> KIP-15 (close): 10 mins
> * semantics of close() and close(timeout)
>
> KIP-13 (quota):
> * protocol change to reflect the state of throttling
> * dependency on using the new metrics package
> * dependency KIP-5 (broker configuration)
>
> Thanks,
>
> Jun
>

Reply via email to