[jira] [Created] (KAFKA-6441) FetchRequest populates buffer of size MinBytes, even if response is smaller

Ivan Babrou created KAFKA-6441: -- Summary: FetchRequest populates buffer of size MinBytes, even if response is smaller Key: KAFKA-6441 URL: https://issues.apache.org/jira/browse/KAFKA-6441 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk8 #2324

See Changes: [wangguoz] KAFKA-6383: Complete shut down for streams threads that have not started -- [...truncated 3.88 MB...] org.apache.kafka.connect.runtime.Transformat

Jenkins build is back to normal : kafka-trunk-jdk7 #3090

See

[jira] [Resolved] (KAFKA-6383) StreamThread.shutdown doesn't clean up completely when called before StreamThread.start

[ https://issues.apache.org/jira/browse/KAFKA-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6383. -- Resolution: Fixed Issue resolved by pull request 4382 [https://github.com/apache/kafka/pull/4382

Build failed in Jenkins: kafka-trunk-jdk8 #2323

See Changes: [ibobrik] KAFKA-4711: fix docs on unclean.leader.election.enable default -- [...truncated 1.42 MB...] org.apache.kafka.common.config.ConfigDefTest > testValid

Build failed in Jenkins: kafka-trunk-jdk7 #3089

See Changes: [ibobrik] KAFKA-4711: fix docs on unclean.leader.election.enable default -- [...truncated 410.18 KB...] kafka.tools.ConsoleProducerTest > testInvalidConfigs

Re: [VOTE] KIP-219 - Improve Quota Communication

Hi, Jiangjie, Thanks for the updated KIP. +1 Jun On Mon, Jan 8, 2018 at 7:45 PM, Becket Qin wrote: > Thanks for the comments, Jun. > > 1. Good point. > 2. Also makes sense. Usually the connection.max.idle.ms is high enough so > the throttling is impacted. > > I have updated the KIP to reflect

Re: [DISCUSS] KIP-232: Detect outdated metadata by adding ControllerMetadataEpoch field

Hi, Dong, My replies are the following. 60. What you described could also work. The drawback is that we will be unnecessarily changing the partition epoch when a partition hasn't really changed. I was imagining that the partition epoch will be stored in /brokers/topics/[topic]/partitions/[partiti

Re: Documentation changes

Hi, Ivan, Thanks for the PR. Sorry for the delay. Just merged it. Jun On Wed, Jan 10, 2018 at 12:56 PM, Ivan Babrou wrote: > What does it take to merge a documentation change? > > * https://github.com/apache/kafka/pull/3567 > > Seeing zero activity is very discouraging. >

Documentation changes

What does it take to merge a documentation change? * https://github.com/apache/kafka/pull/3567 Seeing zero activity is very discouraging.

Build failed in Jenkins: kafka-trunk-jdk7 #3088

See Changes: [wangguoz] KAFKA-6398: fix KTable.filter that does not include its parent's -- [...truncated 398.83 KB...] kafka.server.epoch.LeaderEpochFileCacheTest > shoul

[jira] [Created] (KAFKA-6440) Expose Connect leader via REST

Ryan P created KAFKA-6440: - Summary: Expose Connect leader via REST Key: KAFKA-6440 URL: https://issues.apache.org/jira/browse/KAFKA-6440 Project: Kafka Issue Type: Improvement Components:

Re: [VOTE] KIP-226 - Dynamic Broker Configuration

The vote has passed with 4 binding votes (Gwen, Jun, Jason, me) and 2 non-binding votes (Ted You, Tom Bentley). Many thanks for the reviews and votes. I will update the KIP page. Regards, Rajini On Tue, Jan 9, 2018 at 11:00 AM, Rajini Sivaram wrote: > > Thank you, Jun! I have updated the KIP.

[jira] [Created] (KAFKA-6439) We are using streamset to produce data into kafka topic (3 node cluster). We are facing following error frequently in production.

srithar durairaj created KAFKA-6439: --- Summary: We are using streamset to produce data into kafka topic (3 node cluster). We are facing following error frequently in production. Key: KAFKA-6439 URL: https://iss

[jira] [Created] (KAFKA-6438) NSEE while concurrently creating and deleting a topic

Adam Kotwasinski created KAFKA-6438: --- Summary: NSEE while concurrently creating and deleting a topic Key: KAFKA-6438 URL: https://issues.apache.org/jira/browse/KAFKA-6438 Project: Kafka Iss

[jira] [Created] (KAFKA-6437) Streams does not warn about missing input topics, but hangs

Chris Schwarzfischer created KAFKA-6437: --- Summary: Streams does not warn about missing input topics, but hangs Key: KAFKA-6437 URL: https://issues.apache.org/jira/browse/KAFKA-6437 Project: Kafk

[jira] [Resolved] (KAFKA-2331) Kafka does not spread partitions in a topic among all consumers evenly

[ https://issues.apache.org/jira/browse/KAFKA-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2331. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-2329) Consumers balance fails when multiple consumers are started simultaneously.

[ https://issues.apache.org/jira/browse/KAFKA-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2329. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-2025) In multi-consumer setup - explicit commit, commits on all partitions

[ https://issues.apache.org/jira/browse/KAFKA-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2025. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

Thanks Rajini. Sounds good. Ismael On Wed, Jan 10, 2018 at 11:41 AM, Rajini Sivaram wrote: > Hi Ismael, > > I have updated the KIP to use AES-256 if available and AES-128 otherwise > for password encryption. Looking at GCM, it looks like GCM is typically > used with a variable initialization ve

Jenkins build is back to normal : kafka-trunk-jdk7 #3087

See

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

Hi Ismael, I have updated the KIP to use AES-256 if available and AES-128 otherwise for password encryption. Looking at GCM, it looks like GCM is typically used with a variable initialization vector, while we are using a random, but constant IV per-password. Also, AES/GCM is not supported by Java7

[jira] [Resolved] (KAFKA-1229) Reload broker config without a restart

[ https://issues.apache.org/jira/browse/KAFKA-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1229. -- Resolution: Duplicate Resolving as duplicate of KIP-226/KAFKA-6240. Pls reopen of any concern. > Reload

[jira] [Resolved] (KAFKA-6412) Improve synchronization in CachingKeyValueStore methods

[ https://issues.apache.org/jira/browse/KAFKA-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6412. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4372 [https://github.com/

Re: [DISCUSS] KIP-208: Add SSL support to Kafka Connect REST interface

I'm sorry guys, I'm a bit busy with something else this week. But I will get back to his till the end of the week. Thanks & Regards Jakub On Tue, Jan 9, 2018 at 1:19 AM, Ewen Cheslack-Postava wrote: > On Mon, Jan 8, 2018 at 11:39 AM, Randall Hauch wrote: > > > Nice feedback, Ewen. Thanks! > >