Build failed in Jenkins: kafka-0.11.0-jdk7 #409

See Changes: [wangguoz] MINOR: improve QueryableStateIntegrationTest (#5988) -- [...truncated 287.60 KB...] kafka.utils.UtilsTest > testCircularIterator STARTED kafka.ut

[jira] [Created] (KAFKA-7694) Support ZooKeeper based master/secret key management for delegation tokens

Manikumar created KAFKA-7694: Summary: Support ZooKeeper based master/secret key management for delegation tokens Key: KAFKA-7694 URL: https://issues.apache.org/jira/browse/KAFKA-7694 Project: Kafka

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Yes, I think it makes sense to let KafkaStreams to expose embedded consumer client-id and instance-ids, e.g. at the ThreadMetadata exposed via `localThreadsMetadata`. I can open up a new KIP for the change on Streams side so that we can keep this KIP as on consumer side only. Guozhang On Fri,

[jira] [Resolved] (KAFKA-7235) Use brokerZkNodeVersion to prevent broker from processing outdated controller request

[ https://issues.apache.org/jira/browse/KAFKA-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7235. Resolution: Fixed Fix Version/s: 2.2.0 merged to trunk. > Use brokerZkNodeVersion to prevent broker

[DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

Hello dev, I hope to initiate the discussion for KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions. KIP: < https://cwiki.apache.org/confluence/display/KAFKA/KIP-399%3A+Extend+ProductionExceptionHandler+to+cover+serialization+exceptions > JIRA: https://issues.apache.or

[jira] [Resolved] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1120. Resolution: Fixed Assignee: Zhanxiang (Patrick) Huang (was: Mickael Maison) This is fixed by KAFKA-7

[jira] [Created] (KAFKA-7692) updateFirstUnstableOffset NPE due to sequenceId overflow in ProducerStateManager.append

Ming Liu created KAFKA-7692: --- Summary: updateFirstUnstableOffset NPE due to sequenceId overflow in ProducerStateManager.append Key: KAFKA-7692 URL: https://issues.apache.org/jira/browse/KAFKA-7692 Project:

[jira] [Created] (KAFKA-7693) "IllegalArgumentException: Invalid negative sequence number used" in Kafka Client

Ming Liu created KAFKA-7693: --- Summary: "IllegalArgumentException: Invalid negative sequence number used" in Kafka Client Key: KAFKA-7693 URL: https://issues.apache.org/jira/browse/KAFKA-7693 Project: Kafka

Re: [DISCUSS] KIP-378: Enable Dependency Injection for Kafka Streams handlers

Hello Guozhang, sure, the first approach is very straight-forward and allows minimal changes to the Kafka Streams API. On the other hand, second approach with the interface implementation looks more cleaner to me. I totally agree that this should be first discussed before will be implemented.

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

The updated title sounds fine to me. Ismael On Sun, Dec 2, 2018, 5:25 AM Dongjin Lee Hi Ismael, > > Got it. Your direction is perfectly reasonable. I am now updating the KIP > document and the implementation. > > By allowing the buffer/block size to be configurable, it would be better to > updat

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

Hi Ismael, Got it. Your direction is perfectly reasonable. I am now updating the KIP document and the implementation. By allowing the buffer/block size to be configurable, it would be better to update the title of the KIP like 'Allow fine-grained configuration for compression'. Is that right? @O

Re: [DISCUSS] KIP-394: Require member.id for initial join group request

In fact, it's probably better to move KIP-394 to the vote stage first, so that it's easier to finalize the timeline and smooth the rollout plan for KIP-345. Jason and Stanislav, since y