Jenkins build is back to normal : kafka-trunk-jdk8 #3721

See

[jira] [Created] (KAFKA-8532) controller-event-thread deadlock with zk-session-expiry-handler0

leibo created KAFKA-8532: Summary: controller-event-thread deadlock with zk-session-expiry-handler0 Key: KAFKA-8532 URL: https://issues.apache.org/jira/browse/KAFKA-8532 Project: Kafka Issue Type:

Re: Kafka streams issue

After adding more logging details, we found that we hadn't created topics yet for the consumer & producer for the streams application. We've added a check when starting up to verify that the topics exist, otherwise we exit our app. We're not dynamically creating topics and we want to create them

Re: Permission to create AIP

Hello Elliott, Did you mean Kafka or Airflow? Maybe you happen to jump on a different mailing list :) Guozhang On Wed, Jun 12, 2019 at 3:09 PM Elliott Shugerman < eshuger...@medianewsgroup.com> wrote: > Hello, > > Please grant me permission to create an Airflow Enhancement Proposal. > My

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

See Changes: [jason] KAFKA-8500; Static member rejoin should always update member.id (#6899) [jason] MINOR: Seal the HostedPartition enumeration (#6917) [github] KAFKA-8483/KAFKA-8484; Ensure safe handling of

[VOTE] 2.3.0 RC2

Hi all, We discovered some problems with the first release candidate (RC1) of 2.3.0. Specifically, KAFKA-8484 and KAFKA-8500. I have created a new release candidate that includes fixes for these issues. Check out the release notes for the 2.3.0 release here:

Re: [VOTE] KIP-464: Defaults for AdminClient#createTopic

Good idea, this will prevent a couple of headaches. Regards Patrik > Am 13.06.2019 um 00:24 schrieb Matthias J. Sax : > > We want to make a small additional change and piggy-back it to this KIP. > > To exploit the new feature of AdmintClient in KafkaStreams, we want to > update the default

Re: [DISCUSS] KIP-467: Augment ProduceResponse error messaging

Hi, Guozhang, Thanks for the KIP. A few comments below. 1. "If the error_records is not empty and the error code is not API exception and is not retriable, still retry by creating a new batch ". InvalidTimestampException is an ApiException. It seems we should still retry the non-error records in

Re: [VOTE] KIP-464: Defaults for AdminClient#createTopic

We want to make a small additional change and piggy-back it to this KIP. To exploit the new feature of AdmintClient in KafkaStreams, we want to update the default value of Streams configuration parameter `replication.factor` from `1` to `-1`. This config change will of course only go into 2.4

[jira] [Created] (KAFKA-8531) Change default replication factor config

Matthias J. Sax created KAFKA-8531: -- Summary: Change default replication factor config Key: KAFKA-8531 URL: https://issues.apache.org/jira/browse/KAFKA-8531 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-8530) Consumer should handle authorization errors in OffsetFetch

Jason Gustafson created KAFKA-8530: -- Summary: Consumer should handle authorization errors in OffsetFetch Key: KAFKA-8530 URL: https://issues.apache.org/jira/browse/KAFKA-8530 Project: Kafka

Permission to create AIP

Hello, Please grant me permission to create an Airflow Enhancement Proposal. My cwiki.apache.org username is "eeshugerman". Thanks! Elliott

Re: KIP-457: Add DISCONNECTED state to Kafka Streams

Hi Richard, Sorry for getting late on this, I've finally get some time to take a look at https://github.com/apache/kafka/pull/6594 as well as the KIP itself. Here are some thoughts: 1. The main motivation of this KIP is to be able to distinguish the case where a. "Streams client is in an

[jira] [Resolved] (KAFKA-8484) ProducerId reset can cause IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8484. Resolution: Fixed > ProducerId reset can cause IllegalStateException >

[jira] [Resolved] (KAFKA-8483) Possible reordering of messages by producer after UNKNOWN_PRODUCER_ID error

[ https://issues.apache.org/jira/browse/KAFKA-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8483. Resolution: Fixed Fix Version/s: 2.3.0 > Possible reordering of messages by

Re: [DISCUSS] KIP-467: Augment ProduceResponse error messaging

Hi Kamal, I intend to scope KIP-467 for producer <--> brokers interaction only, so that we can have a small enough one to discuss and tackle. I've just read about KIP-334 as well and I feel it's still better to be addressed independently by itself. LMK what you think. Guozhang On Mon, Jun 10,

[jira] [Reopened] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reopened KAFKA-7190: -- Assignee: Guozhang Wang (was: lambdaliu) Reopening this issue since broker would

[jira] [Created] (KAFKA-8529) Flakey test ConsumerBounceTest#testCloseDuringRebalance

Boyang Chen created KAFKA-8529: -- Summary: Flakey test ConsumerBounceTest#testCloseDuringRebalance Key: KAFKA-8529 URL: https://issues.apache.org/jira/browse/KAFKA-8529 Project: Kafka Issue

Re: [VOTE] KIP-476: Add Java AdminClient interface

I'm not married to that part. That was only done to keep it more or less inline with what's already there, (an abstract class that has a factory method that returns a subclass sounds like the same anti-pattern ;)) An alternative would to have an `AdminClients` utility class to create the

Re: [VOTE] KIP-476: Add Java AdminClient interface

With 3.0 not imminent I would prefer to make this change soon, rather than later. On Tue, 11 Jun 2019 at 21:46, Colin McCabe wrote: > On Tue, Jun 11, 2019, at 12:12, Andy Coates wrote: > > Thanks for the response Colin, > > > > > What specific benefits do we get from transitioning to using an >

Re: [VOTE] KIP-476: Add Java AdminClient interface

Thanks Great. Do that mean you're a +1? On Tue, 11 Jun 2019 at 21:46, Colin McCabe wrote: > On Tue, Jun 11, 2019, at 12:12, Andy Coates wrote: > > Thanks for the response Colin, > > > > > What specific benefits do we get from transitioning to using an > interface > > > rather than an abstract

Re: [DISCUSS] KIP-466: Add support for List serialization and deserialization

Hmm the formatting got removed unfortunately. I’m sorry, it got harder to read my email. > On Jun 12, 2019, at 10:27 AM, Development wrote: > > Hi Matthias, > > Indeed, you are right. I missed your email, I had a problem with my mail > server, so I guess I didn’t receive it. > > 1) Here is

Re: [DISCUSS] KIP-466: Add support for List serialization and deserialization

Hi Matthias, Indeed, you are right. I missed your email, I had a problem with my mail server, so I guess I didn’t receive it. 1) Here is what I came up with In my ListSerializer.java I have the following: try (final DataOutputStream out = new DataOutputStream(baos)) { // I’m encoding the

[jira] [Resolved] (KAFKA-8514) Kafka clients should not include Scala's Java 8 compatibility lib

[ https://issues.apache.org/jira/browse/KAFKA-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8514. Resolution: Fixed Fix Version/s: 2.3.0 > Kafka clients should not include Scala's Java 8

Re: [VOTE] KIP-412: Extend Admin API to support dynamic application log levels

Hello, I finished work on an initial PR for this KIP, it is ready for review here - https://github.com/apache/kafka/pull/6903 During implementation, I noticed a couple of holes in the KIP and did the following changes: * add LogLevelConfig public class and a few more log levels (7 total - ALL,

Jenkins build is back to normal : kafka-trunk-jdk8 #3718

See

[jira] [Created] (KAFKA-8528) Trogdor - Expose Trogdor-specific JMX metrics

Stanislav Kozlovski created KAFKA-8528: -- Summary: Trogdor - Expose Trogdor-specific JMX metrics Key: KAFKA-8528 URL: https://issues.apache.org/jira/browse/KAFKA-8528 Project: Kafka

[jira] [Resolved] (KAFKA-7597) Trogdor - Support transactions in ProduceBenchWorker

[ https://issues.apache.org/jira/browse/KAFKA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-7597. Resolution: Fixed > Trogdor - Support transactions in ProduceBenchWorker >

Re: Kafka streams issue

Does the application transit to RUNNING state? Also check `KafkaStreams#localThreadsMetadata()` what tasks are assigned? You might also enable DEBUG logs for `org.apache.kafka.clients.consumer.**` classes to see if the consumer sends fetch request to the broker. -Matthias On 6/11/19 7:03 PM,