[jira] [Created] (KAFKA-8041) Flaky Test LogDirFailureTest#testIOExceptionDuringLogRoll

Matthias J. Sax created KAFKA-8041: -- Summary: Flaky Test LogDirFailureTest#testIOExceptionDuringLogRoll Key: KAFKA-8041 URL: https://issues.apache.org/jira/browse/KAFKA-8041 Project: Kafka

Build failed in Jenkins: kafka-2.0-jdk8 #236

See Changes: [jason] KAFKA-8002: Log dir reassignment stalls if future replica has different -- [...truncated 896.17 KB...] kafka.zk.ReassignPartitionsZNodeTest >

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

See Changes: [rhauch] improve some logging statements (#6078) [rhauch] KAFKA-7880:Naming worker thread by task id (#6275) -- [...truncated 2.32 MB...]

Build failed in Jenkins: kafka-2.2-jdk8 #43

See Changes: [manikumar] KAFKA-7312: Change broker port used in testMinimumRequestTimeouts and -- [...truncated 2.73 MB...] kafka.coordinator.group.GroupCoordinatorTest >

[jira] [Created] (KAFKA-8040) Streams needs to retry initTransactions

John Roesler created KAFKA-8040: --- Summary: Streams needs to retry initTransactions Key: KAFKA-8040 URL: https://issues.apache.org/jira/browse/KAFKA-8040 Project: Kafka Issue Type: Improvement

Build failed in Jenkins: kafka-1.1-jdk7 #251

See Changes: [jason] KAFKA-8002: Log dir reassignment stalls if future replica has different -- [...truncated 1.94 MB...]

Guava version upgrade

Hello, when downloading Kafka 2.1.1, the kafka_2.12-2.1.1.tgz still contains guava-20.0.jar. This guava version currently has a vulnerability described here: https://github.com/google/guava/wiki/CVE-2018-10237 The version 24.1.1 and 25.0+ are fixed version. Are there any plans to upgrade this

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Hi all, I don't have too much time to respond at the moment, but I don't have much to say anyway. I just wanted to respond to your requests for more opinions. The point Matthias brought up is a good one. I think this was similar to Jan's concern before about "swallowing" some intermediate

[jira] [Resolved] (KAFKA-8002) Replica reassignment to new log dir may not complete if future and current replicas segment files have different base offsets

[ https://issues.apache.org/jira/browse/KAFKA-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8002. Resolution: Fixed Fix Version/s: 2.1.2 2.0.2

[jira] [Created] (KAFKA-8039) Flaky Test SaslAuthenticatorTest#testCannotReauthenticateAgainFasterThanOneSecond

Matthias J. Sax created KAFKA-8039: -- Summary: Flaky Test SaslAuthenticatorTest#testCannotReauthenticateAgainFasterThanOneSecond Key: KAFKA-8039 URL: https://issues.apache.org/jira/browse/KAFKA-8039

[jira] [Created] (KAFKA-8038) Flaky Test SslTransportLayerTest#testCloseSsl

Matthias J. Sax created KAFKA-8038: -- Summary: Flaky Test SslTransportLayerTest#testCloseSsl Key: KAFKA-8038 URL: https://issues.apache.org/jira/browse/KAFKA-8038 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-8037) KTable restore may load bad data

Matthias J. Sax created KAFKA-8037: -- Summary: KTable restore may load bad data Key: KAFKA-8037 URL: https://issues.apache.org/jira/browse/KAFKA-8037 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-7651) Flaky test SaslSslAdminClientIntegrationTest.testMinimumRequestTimeouts

[ https://issues.apache.org/jira/browse/KAFKA-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7651. -- Resolution: Fixed Fix Version/s: 2.2.1 2.1.2 2.0.2 This

[jira] [Resolved] (KAFKA-7312) Transient failure in kafka.api.AdminClientIntegrationTest.testMinimumRequestTimeouts

[ https://issues.apache.org/jira/browse/KAFKA-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7312. -- Resolution: Fixed Fix Version/s: (was: 2.3.0) 2.1.2

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Thanks Adam, *> Q) Range scans work with caching enabled, too. Thus, there is no functional/correctness requirement to disable caching. I cannot remember why Jan's proposal added this? It might be an implementation detail though (maybe just remove it from the KIP? -- might be miss leading). *>

Re: [DISCUSS] KIP-434: Add Replica Fetcher and Log Cleaner Count Metrics

Hey Viktor, > however displaying the thread count (be it alive or dead) would still add extra information regarding the failure, that a thread died during cleanup. I agree, I think it's worth adding. > Doing this on the replica fetchers though would be a bit harder as the number of replica

Re: [DISCUSS] KIP-429 : Smooth Auto-Scaling for Kafka Streams

Thanks Guozhang for the great questions. Answers are inlined: 1. I'm still not sure if it's worthwhile to add a new type of "learner task" in addition to "standby task": if the only difference is that for the latter, we would consider workload balance while for the former we would not, I think we

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Hi Matthias Thank you for the feedback! I appreciate your well thought-out questions. I have tried to answer and comment on everything that I know below. *> Q) For the materialized combined-key store, why do we need to disable> caching? And why do we need to flush the store?* This is an

[jira] [Created] (KAFKA-8036) Log dir reassignment on followers fails with FileNotFoundException for the leader epoch cache on leader election

Stanislav Kozlovski created KAFKA-8036: -- Summary: Log dir reassignment on followers fails with FileNotFoundException for the leader epoch cache on leader election Key: KAFKA-8036 URL:

Re: Apache Kafka Memory Leakage???

Hi Syed, and you are sure that this memory is actually allocated? I still have my reservations about that metric to be honest. Is there any way to connect to the process with for example jconsole and having a look at memory consumption in there? Or alternatively, since the code you have sent is

Re: Apache Kafka Memory Leakage???

Sonke, thanks again. Yes, I replaced the non-kafka code from our end with a simple Sysout statement as follows: do { ConsumerRecords records = consumer.poll(Duration.of(timeout, ChronoUnit.MILLIS)); for (final ConsumerRecord record : records) { if (!infiniteLoop &&

[jira] [Created] (KAFKA-8035) Add tests for generic bounds for KStream API

Bruno Cadonna created KAFKA-8035: Summary: Add tests for generic bounds for KStream API Key: KAFKA-8035 URL: https://issues.apache.org/jira/browse/KAFKA-8035 Project: Kafka Issue Type: Test

Re: Apache Kafka Memory Leakage???

Hi Syed, let's keep it on the list for now so that everybody can participate :) The different .poll() method was just an unrelated observation, the main points of my mail were the question about whether this is the correct metric you are looking at and replacing the payload of your code with a