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

See Changes: [github] KAFKA-9441: Add internal TransactionManager (#8105) [github] KAFKA-9577; SaslClientAuthenticator incorrectly negotiates -- [...truncated 2.89

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Hi Vito, I checked the code and I think you are right. If a user provides a wrong partition there will be NPE at tasks.get(keyTaskId).getStore(storeName) as that task is not available at this machine. I think we split the line: 

[DISCUSS] KIP-572: Improve timeouts and retires in Kafka Streams

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I would like to propose KIP-572 to make Kafka Streams more robust with regard to timeout exception handling. https://cwiki.apache.org/confluence/display/KAFKA/KIP-572%3A+Improve+tim eouts+and+retries+in+Kafka+Streams Note, that there is a

[jira] [Created] (KAFKA-9596) Hanging test case `testMaxLogCompactionLag`

Jason Gustafson created KAFKA-9596: -- Summary: Hanging test case `testMaxLogCompactionLag` Key: KAFKA-9596 URL: https://issues.apache.org/jira/browse/KAFKA-9596 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-9577) Client encountering SASL_HANDSHAKE protocol version errors on 2.5 / trunk

[ https://issues.apache.org/jira/browse/KAFKA-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9577. Resolution: Fixed > Client encountering SASL_HANDSHAKE protocol version errors on 2.5 /

Jenkins build is back to normal : kafka-2.5-jdk8 #39

See

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

See Changes: [github] MINOR: Standby task commit needed when offsets updated (#8146) [me] MINOR: Document endpoints for connector topic tracking (KIP-558) --

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Hi, Matthias and Navinder, I have a question about the valid partition in StreamThreadStateStoreProvider. In the StreamThreadStateStoreProvider#createKeyTaskId(storeName, partition):

[jira] [Created] (KAFKA-9595) Config tool should use admin client's incremental config API

Jason Gustafson created KAFKA-9595: -- Summary: Config tool should use admin client's incremental config API Key: KAFKA-9595 URL: https://issues.apache.org/jira/browse/KAFKA-9595 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk11 #1181

See Changes: [github] KAFKA-9206; Throw KafkaException on CORRUPT_MESSAGE error in Fetch [github] MINOR: Standby task commit needed when offsets updated (#8146) [me] MINOR: Document endpoints for connector

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Hello, Just to make some updates. I changed the name of the metric so that it was more in line with usual Kafka naming conventions for metrics / sensors. Below is the updated description of the metric: dropped-idempotent-updates : (Level 2 - Per Task) DEBUG (rate | total) Description: This

Build failed in Jenkins: kafka-2.5-jdk8 #38

See Changes: [github] KAFKA-9582: Do not abort transaction in unclean close (#8143) [wangguoz] MINOR: Improve EOS example exception handling (#8052) -- [...truncated 2.90

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Hi all, Thanks for the clarification. I was just confused a little on what was going on. So I guess then that for the actual proposal. We got the following: 1. We check for binary equality, and perform no extra look ups. 2. Emphasize that this applies only to materialized tables. 3. We drop

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

See Changes: [github] KAFKA-9206; Throw KafkaException on CORRUPT_MESSAGE error in Fetch -- [...truncated 2.88 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Jenkins build is back to normal : kafka-trunk-jdk11 #1180

See

Re: Discussion thread for KIP-X

Hey Rangan, thanks for the interest! In fact we are still in the design phase, and need more supporting use cases that requires a higher scaling factor than number of partitions. It would be good if you could share some of your needed use case when the unit time of processing one record is the

[jira] [Created] (KAFKA-9594) speed up the processing of LeaderAndIsrRequest

Manikumar created KAFKA-9594: Summary: speed up the processing of LeaderAndIsrRequest Key: KAFKA-9594 URL: https://issues.apache.org/jira/browse/KAFKA-9594 Project: Kafka Issue Type: Improvement

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

See Changes: [manikumar] MINOR: Remove unwanted regexReplace on tests/kafkatest/__init__.py -- [...truncated 2.88 MB...] org.apache.kafka.streams.TopologyTestDriverTest

[jira] [Created] (KAFKA-9593) Kafka config allows updating a nonexistent config and makes it mandatory to specify the config for further config updates

Aishwarya Gune created KAFKA-9593: - Summary: Kafka config allows updating a nonexistent config and makes it mandatory to specify the config for further config updates Key: KAFKA-9593 URL:

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Hi Bruno, Thanks for the clarification. Indeed, I was thinking two things: 1. For the initial implementation, we can just avoid adding any extra lookups, but only do the comparison when we already happen to have the prior value. 2. I think, as a result of the timestamp semantics, we actually _do_

Build failed in Jenkins: kafka-2.5-jdk8 #37

See Changes: [manikumar] KAFKA-9586: Fix errored json filename in ops documentation -- [...truncated 2.90 MB...] org.apache.kafka.streams.TestTopicsTest >

Re: Discussion thread for KIP-X

cc @Boyang Chen who authored this draft. Guozhang On Fri, Feb 21, 2020 at 10:29 AM Rangan Prabhakaran (BLOOMBERG/ 919 3RD A) < kprabhaka...@bloomberg.net> wrote: > Hi, > A few of us have been following KIP-X. We are interested in the roadmap / > plan there and would like to contribute towards

[jira] [Created] (KAFKA-9592) Safely abort Producer transactions during application shutdown

Boyang Chen created KAFKA-9592: -- Summary: Safely abort Producer transactions during application shutdown Key: KAFKA-9592 URL: https://issues.apache.org/jira/browse/KAFKA-9592 Project: Kafka

Discussion thread for KIP-X

Hi, A few of us have been following KIP-X. We are interested in the roadmap / plan there and would like to contribute towards the same. What are the next steps to discuss / iterate on this KIP ? Currently, its in draft state and there does not seem to be a discussion thread attached yet.

[jira] [Resolved] (KAFKA-9206) Consumer should handle `CORRUPT_MESSAGE` error code in fetch response

[ https://issues.apache.org/jira/browse/KAFKA-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9206. Fix Version/s: 2.6.0 Resolution: Fixed > Consumer should handle `CORRUPT_MESSAGE`

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

See

Build failed in Jenkins: kafka-trunk-jdk11 #1179

See Changes: [manikumar] KAFKA-9575: Mention ZooKeeper 3.5.7 upgrade [manikumar] KAFKA-9586: Fix errored json filename in ops documentation -- [...truncated 5.85

Build failed in Jenkins: kafka-2.5-jdk8 #36

See Changes: [manikumar] KAFKA-9575: Mention ZooKeeper 3.5.7 upgrade -- [...truncated 2.90 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Created] (KAFKA-9591) Log clearer error messages when there is an offset out of range (Client Change)

Cheng Tan created KAFKA-9591: Summary: Log clearer error messages when there is an offset out of range (Client Change) Key: KAFKA-9591 URL: https://issues.apache.org/jira/browse/KAFKA-9591 Project: Kafka

Re: [DISCUSS] KIP-570: Add leader epoch in StopReplicaRequest

I have updated the KIP. I will start a vote on Monday if there are no further comments by then. Best, David On Wed, Feb 19, 2020 at 5:59 PM David Jacot wrote: > Hey Jason, > > You're right. The leader epoch is not bumped when a topic is deleted. Using > a sentinel (e.g. -1) which would

[jira] [Created] (KAFKA-9590) Add read-only configuration to limit number of topic partitions

Gokul Ramanan Subramanian created KAFKA-9590: Summary: Add read-only configuration to limit number of topic partitions Key: KAFKA-9590 URL: https://issues.apache.org/jira/browse/KAFKA-9590

Fix of System tests on JDK11

Hello, Kafka team. I found that system tests that starts earlier versions of Kafka doesn’t work with JDK11 [1] There is two main reason for it: * Kafka startup scripts contains removed JVM options like `-XX:+PrintGCDateStamps or `-XX:UseParNewGC`. * 0.10.0.1, 0.10.1.1, 0.10.2.2,

[jira] [Resolved] (KAFKA-9586) Fix errored json filename in ops documentation

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

[jira] [Resolved] (KAFKA-9575) "Notable changes in 2.5.0" doesn't mention ZooKeeper 3.5.7

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

[DISCUSS] KIP-573: Enable TLSv1.3 by default

Hello, I'd like to start a discussion of KIP [1] This is follow-up for the KIP-553 [2] Its goal is to enable TLSv1.3 by default. Your comments and suggestions are welcome. [1] https://cwiki.apache.org/confluence/display/KAFKA/KIP-573%3A+Enable+TLSv1.3+by+default [2]

[jira] [Created] (KAFKA-9589) LogValidatorTest#testLogAppendTimeNonCompressedV2 is not executed and does not pass

Stanislav Kozlovski created KAFKA-9589: -- Summary: LogValidatorTest#testLogAppendTimeNonCompressedV2 is not executed and does not pass Key: KAFKA-9589 URL: https://issues.apache.org/jira/browse/KAFKA-9589

Build failed in Jenkins: kafka-2.4-jdk8 #150

See Changes: [github] KAFKA-6266: Repeated occurrence of WARN Resetting first dirty offset … -- [...truncated 5.56 MB...] org.apache.kafka.streams.test.OutputVerifierTest >