We have a proposal to propagate ISR changes to every broker in KAFKA-1367. Thanks,
Jun On Tue, Jun 2, 2015 at 12:55 PM, Ashish Singh <asi...@cloudera.com> wrote: > Jun, > > Thanks for the notes! > > @Jun/ Joel, An inline question on ISR info in TMR. > > On Tuesday, June 2, 2015, Jun Rao <j...@confluent.io> wrote: > > > The following are my notes. > > > > 1. Security: Harsh will upload a new SSL patch in the next day or two. > > > > 2. KIP-21 (dynamic configuration): > > How to serve DescribeConfigRequest? Currently, topic config is only > cached > > on brokers storing the topic. We will need to either cache the config on > > every broker or read to config from ZK directly. Since > > DescribeConfigRequest is used infrequently, it's probably simpler to > start > > with just reading from ZK. > > > > 3. KIP-19 (Producer request timeout): > > We agreed that option 3 in the wiki is simple and makes the most sense. > > Jiangie will start the voting thread. > > > > 4. KIP-4 (admin command): > > We discussed whether to leave ISR in the TopicMetadataResponse. There is > no > > objection to this. However, Joel will follow up on this to see whether > it's > > better to piggyback ISR in the fetch response itself. > > How are we then addressing incorrect ISR information in > TopicMetadataResponse? > > > > > Thanks, > > > > Jun > > > > > -- > Ashish 🎤h >
