Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #81

See Changes: [github] KAFKA-10482: Fix flaky testDynamicListenerConnectionCreationRateQuota (#9301) -- [...truncated 3.34 MB...]

[jira] [Created] (KAFKA-10516) Implement Topic Command changes

David Jacot created KAFKA-10516: --- Summary: Implement Topic Command changes Key: KAFKA-10516 URL: https://issues.apache.org/jira/browse/KAFKA-10516 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-653: Upgrade log4j to log4j2

Hi Tom, Thanks for the detailed analysis. Recently, I was also thinking about API compatibility. I initially thought that the difference between the root logger name would break the compatibility (as the KIP states), it seems like I found a workaround: 1. When the user requests arrive, regard

Re: [DISCUSS] KIP-516: Topic Identifiers

Hi Tom, Thanks for the comment. I think this is a really good idea and it has been added to the KIP under the newly added tooling section. Thanks again, Justine On Wed, Sep 23, 2020 at 3:17 AM Tom Bentley wrote: > Hi Justine, > > I know you started the vote thread, but on re-reading the KIP I

Re: [DISCUSS] KIP-516: Topic Identifiers

Hi, Justine, Thanks for the response. Made another pass. A few more comments below. 20. znode schema: 20.1 It seems that {"name": "version", "type": "int", "id": "UUID", "doc": "version id"} should be {"name": "version", "type": "int"}, {"name": "id", "type": "UUID", "doc": "version id"}. 20.2

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #80

See

Re: Question Regarding Offset Behavior When Calling Poll()

I guess it depends where the exception comes from? Can you clarify? -Matthias On 9/23/20 12:53 AM, Zhen Zhang wrote: > Hi there, > > I am new to Kafka and I would like to get some clarifications for a newbie > question, > > Let's say if I have set up my consumer's "enable.auto.commit" to

Kafka consumer Exception handling and offset management

Hi Team, Currently I'm implementing Spring boot @kafkalistener. I need to know that what all are the exception that may raise, while try to consume the record from kafka topic. How to commit the current offset after successfully processed the record.In between that I have handle the exception.

Jenkins build is back to normal : Kafka » kafka-trunk-jdk15 #82

See

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #82

See Changes: [github] KAFKA-10514: Advance mock time for state directory cleanup (#9323) -- [...truncated 6.69 MB...]

Re: ApacheCon Bug Bash

Sohil, Is bugsbunnyshah/AIPlatform related to Apache Kafka in some manner? I'm not familiar with it. Regardless, Muse is free to use on public repositories - all you need to do is install the muse app ( https://github.com/apps/muse-dev). Muse will then respond to pull requests with new bugs or

[jira] [Created] (KAFKA-10518) Consumer fetches could be inefficient when lags are unbalanced

Dhruvil Shah created KAFKA-10518: Summary: Consumer fetches could be inefficient when lags are unbalanced Key: KAFKA-10518 URL: https://issues.apache.org/jira/browse/KAFKA-10518 Project: Kafka

Re: ApacheCon Bug Bash

Hi Tom, AIPlatform is no related to Kafka. It is an end-to-end platform for building AI applications. Data Modeling, Deployment, Evolving Data Models using Datasets ingested in the built-in Data Lake etc. Please feel free to include under the “Apache” repos etc. No issues at all. Thanks Sohil

Re: [DISCUSS] KIP-516: Topic Identifiers

Hi Jun, Thanks for the comments. I apologize for some of the typos and confusion. I’ve updated the KIP to fix some of the issues you mentioned. 20.2 I’ve changed the type to String. 20.1/3 I’ve updated the TopicZNode to fix formatting and reflect the latest version before this change. 21. You

[jira] [Created] (KAFKA-10519) Unit tests for VotedState

Jason Gustafson created KAFKA-10519: --- Summary: Unit tests for VotedState Key: KAFKA-10519 URL: https://issues.apache.org/jira/browse/KAFKA-10519 Project: Kafka Issue Type: Sub-task

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

Sorry for the late reply Jason, and thanks for calling it out. After couple if direct discussion with Jason, Colin, Ismael, and John, I agree that we should keep `retries` config for both producer and admin client. I updated the KIP accordingly and opened a PR to revert the deprecation:

[jira] [Created] (KAFKA-10517) Inefficient consumer processing with fetch sessions

Dhruvil Shah created KAFKA-10517: Summary: Inefficient consumer processing with fetch sessions Key: KAFKA-10517 URL: https://issues.apache.org/jira/browse/KAFKA-10517 Project: Kafka Issue

Re: [DISCUSS] KIP-671: Shutdown Streams Application when appropriate exception is thrown

Bruno, I think that we can't guarantee that the message will get propagated perfectly in every case of, say network partitioning, though it will work for many cases. So I would say it's best effort and I will mention it in the kip. As for when to use it I think we can discuss if this will be

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #84

See Changes: [github] KAFKA-10505: Fix parsing of generation log string. (#9312) [github] KAFKA-9450: Follow-up; Forbid process after closed (#9083) --

[jira] [Resolved] (KAFKA-10297) Don't use deprecated producer config `retries`

[ https://issues.apache.org/jira/browse/KAFKA-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-10297. - Resolution: Invalid We change the KIP to not deprecate `retries`. Hence, this ticket is

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #83

See Changes: [github] MINOR: Remove unneeded FIXME (#9330) -- [...truncated 6.69 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #83

See Changes: [github] MINOR: Remove unneeded FIXME (#9330) -- [...truncated 3.35 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[GitHub] [kafka-site] ankit-kumar-25 edited a comment on pull request #220: KAFKA-8360: Docs do not mention RequestQueueSize JMX metric

ankit-kumar-25 edited a comment on pull request #220: URL: https://github.com/apache/kafka-site/pull/220#issuecomment-696188603 Hey @viktorsomogyi, Thank you for the pointers, I have created a PR against the ops.html available in the Kafka project:

[GitHub] [kafka-site] ankit-kumar-25 closed pull request #220: KAFKA-8360: Docs do not mention RequestQueueSize JMX metric

ankit-kumar-25 closed pull request #220: URL: https://github.com/apache/kafka-site/pull/220 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

Re: [DISCUSS] KIP-406: GlobalStreamThread should honor custom reset policy

Thanks a lot John for these suggestions. @Matthias can share your thoughts on the last two comments made in this chain. Thanks,Navinder On Monday, 14 September, 2020, 09:03:32 pm IST, John Roesler wrote: Hi Navinder, Thanks for the reply. I wasn't thinking of an _exponential_

[jira] [Created] (KAFKA-10514) flaky test StateDirectoryTest.shouldLogStateDirCleanerMessage

Chia-Ping Tsai created KAFKA-10514: -- Summary: flaky test StateDirectoryTest.shouldLogStateDirCleanerMessage Key: KAFKA-10514 URL: https://issues.apache.org/jira/browse/KAFKA-10514 Project: Kafka

Question Regarding Offset Behavior When Calling Poll()

Hi there, I am new to Kafka and I would like to get some clarifications for a newbie question, Let's say if I have set up my consumer's "enable.auto.commit" to false, and then poll the records one at a time. So when calling poll(), starting from offset 0, if any exception is thrown, should I

[jira] [Created] (KAFKA-10515) NPE: Foreign key join serde may not be initialized with default serde if application is distributed

Thorsten Hake created KAFKA-10515: - Summary: NPE: Foreign key join serde may not be initialized with default serde if application is distributed Key: KAFKA-10515 URL:

Re: [DISCUSS] KIP-516: Topic Identifiers

Hi Justine, I know you started the vote thread, but on re-reading the KIP I noticed that although the topic id is included in the MetadataResponse it's not surfaced in the output from `kafka-topics.sh --describe`. Maybe that was intentional because ids are intentionally not really something the

Re: [DISCUSS] KIP-653: Upgrade log4j to log4j2

Hi Dongjin, I'd like to see this feature, but if I understand correctly, the KIP in its current form breaks a couple of Kafka APIs. For Kafka Connect it says "From log4j2, the name of the root logger becomes empty string from 'root'. It impacts Kafka connect's dynamic logging control feature.