Below are my notes. Feel free to add/ modify the content. Kafka KIP discussion (May 26, 2015) KIP-12 (sasl/ssl authentication): status check
Not much discussion this time. KIP-21 (configuration management) - Aditya will make changes to KIP-4 based on last time’s discussion. - Andrei is OK with the changes suggested for KIP-4. KIP-19 (Add a request timeout to NetworkClient) - In last KIP hangout it was suggested to just have two timeouts, blocking time during send and how long to wait to really send the message out. However, it is difficult to map all timeouts we currently provide to users to one of the above mentioned timeout categories. - New proposal - let user know what kind of things they have to wait for once they call send. KIP has been updated with the details. - Usecases will be added for different timeout configs to KIP. - Should timeout be specified in api or in the configs? No strong usecase for having it in APIs. For now, buffer full timeout will be in configs. KIP-25 (system test): quick overview - Initial patch with examples on writing system tests using ducktape will be posted soon. - Roadmaps for system tests using ducktape will be added to wiki. - Should we have all new system tests in ducktape? Probably not at this time as ducktape is still under evaluation. However, eventually if we plan to move over to using ducktape for system tests, all old system tests will be ported to use ducktape. On Tue, May 26, 2015 at 8:50 AM, Jun Rao <j...@confluent.io> wrote: > Hi, Everyone, > > We will have a KIP hangout at 11 PST on May 26. The following is the > agenda. If you want to attend and is not on the invite, please let me know. > > Agenda: > KIP-12 (sasl/ssl authentication): status check > KIP-21 (configuration management) > KIP-19 (Add a request timeout to NetworkClient) > KIP-25 (system test): quick overview > > Thanks, > > Jun > -- Regards, Ashish