[jira] [Commented] (KAFKA-12456) Log "Listeners are not identical across brokers" message at WARN/INFO instead of ERROR

[ https://issues.apache.org/jira/browse/KAFKA-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299889#comment-17299889 ] Ismael Juma commented on KAFKA-12456: - I suggest INFO. > Log "Listeners are not ide

[jira] [Updated] (KAFKA-10619) Producer will enable EOS by default

[ https://issues.apache.org/jira/browse/KAFKA-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-10619: Fix Version/s: 3.0.0 > Producer will enable EOS by default > --- >

[jira] [Commented] (KAFKA-12431) Fetch Request/Response without Topic information

[ https://issues.apache.org/jira/browse/KAFKA-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297555#comment-17297555 ] Ismael Juma commented on KAFKA-12431: - Thanks for getting to the bottom of it. I thi

[jira] [Commented] (KAFKA-12431) Fetch Request/Response without Topic information

[ https://issues.apache.org/jira/browse/KAFKA-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297503#comment-17297503 ] Ismael Juma commented on KAFKA-12431: - [~sinitw] Do you see 500ms between fetch resp

[jira] [Commented] (KAFKA-12431) Fetch Request/Response without Topic information

[ https://issues.apache.org/jira/browse/KAFKA-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297435#comment-17297435 ] Ismael Juma commented on KAFKA-12431: - Thanks for the report. What's the `fetch.max.

[jira] [Commented] (KAFKA-12436) deprecate MirrorMaker v1

[ https://issues.apache.org/jira/browse/KAFKA-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296585#comment-17296585 ] Ismael Juma commented on KAFKA-12436: - Removal would have to wait for 4.0 if depreca

[jira] [Commented] (KAFKA-12435) Several streams-test-utils classes missing from javadoc

[ https://issues.apache.org/jira/browse/KAFKA-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296367#comment-17296367 ] Ismael Juma commented on KAFKA-12435: - cc [~mjsax] [~vvcephei] > Several streams-te

[jira] [Commented] (KAFKA-12435) Several streams-test-utils classes missing from javadoc

[ https://issues.apache.org/jira/browse/KAFKA-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296366#comment-17296366 ] Ismael Juma commented on KAFKA-12435: - If you run `aggregatedJavadoc` with Java 8, y

[jira] [Created] (KAFKA-12435) Several streams-test-utils classes missing from javadoc

Ismael Juma created KAFKA-12435: --- Summary: Several streams-test-utils classes missing from javadoc Key: KAFKA-12435 URL: https://issues.apache.org/jira/browse/KAFKA-12435 Project: Kafka Issue T

[jira] [Updated] (KAFKA-12435) Several streams-test-utils classes missing from javadoc

[ https://issues.apache.org/jira/browse/KAFKA-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12435: Description: !image-2021-03-05-14-22-45-891.png! Only 3 of them show up currently ^. Source:  htt

[jira] [Resolved] (KAFKA-12415) Prepare for Gradle 7.0 and restrict transitive scope for non api dependencies

[ https://issues.apache.org/jira/browse/KAFKA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-12415. - Resolution: Fixed > Prepare for Gradle 7.0 and restrict transitive scope for non api dependencie

[jira] [Created] (KAFKA-12418) Make sure it's ok not to include test jars in the release tarball

Ismael Juma created KAFKA-12418: --- Summary: Make sure it's ok not to include test jars in the release tarball Key: KAFKA-12418 URL: https://issues.apache.org/jira/browse/KAFKA-12418 Project: Kafka

[jira] [Created] (KAFKA-12417) streams module should use `testRuntimeClasspath` instead of `testRuntime` configuration

Ismael Juma created KAFKA-12417: --- Summary: streams module should use `testRuntimeClasspath` instead of `testRuntime` configuration Key: KAFKA-12417 URL: https://issues.apache.org/jira/browse/KAFKA-12417

[jira] [Created] (KAFKA-12415) Prepare for Gradle 7.0 and restrict transitive scope for non api dependencies

Ismael Juma created KAFKA-12415: --- Summary: Prepare for Gradle 7.0 and restrict transitive scope for non api dependencies Key: KAFKA-12415 URL: https://issues.apache.org/jira/browse/KAFKA-12415 Project:

[jira] [Commented] (KAFKA-12394) Consider topic id existence and authorization errors

[ https://issues.apache.org/jira/browse/KAFKA-12394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293197#comment-17293197 ] Ismael Juma commented on KAFKA-12394: - Ah, yes. "topic IDs are not considered sensit

[jira] [Commented] (KAFKA-12394) Consider topic id existence and authorization errors

[ https://issues.apache.org/jira/browse/KAFKA-12394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293155#comment-17293155 ] Ismael Juma commented on KAFKA-12394: - {quote}There is an argument to be made for TO

[jira] [Updated] (KAFKA-12386) Flush unflushed segments during recovery

[ https://issues.apache.org/jira/browse/KAFKA-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12386: Description: We could strengthen the guarantees kafka provides after an unclean shutdown by flush

[jira] [Created] (KAFKA-12386) Flush unflushed segments during recovery

Ismael Juma created KAFKA-12386: --- Summary: Flush unflushed segments during recovery Key: KAFKA-12386 URL: https://issues.apache.org/jira/browse/KAFKA-12386 Project: Kafka Issue Type: Improvemen

[jira] [Updated] (KAFKA-10101) recovery point is advanced without flushing the data after recovery

[ https://issues.apache.org/jira/browse/KAFKA-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-10101: Fix Version/s: 2.8.0 > recovery point is advanced without flushing the data after recovery > -

[jira] [Commented] (KAFKA-12365) Block transactional APIs running kip-500 (for now)

[ https://issues.apache.org/jira/browse/KAFKA-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289613#comment-17289613 ] Ismael Juma commented on KAFKA-12365: - I would disable this and the kip-500 variant

[jira] [Resolved] (KAFKA-12341) Duplicate javassist library found in broker classpath

[ https://issues.apache.org/jira/browse/KAFKA-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-12341. - Resolution: Fixed > Duplicate javassist library found in broker classpath >

[jira] [Updated] (KAFKA-12235) ZkAdminManager.describeConfigs returns no config when 2+ configuration keys are specified

[ https://issues.apache.org/jira/browse/KAFKA-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12235: Labels: regression (was: ) > ZkAdminManager.describeConfigs returns no config when 2+ configurati

[jira] [Updated] (KAFKA-12235) ZkAdminManager.describeConfigs returns no config when 2+ configuration keys are specified

[ https://issues.apache.org/jira/browse/KAFKA-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12235: Fix Version/s: 2.8.0 > ZkAdminManager.describeConfigs returns no config when 2+ configuration keys

[jira] [Updated] (KAFKA-12235) ZkAdminManager.describeConfigs returns no config when 2+ configuration keys are specified

[ https://issues.apache.org/jira/browse/KAFKA-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12235: Priority: Critical (was: Major) > ZkAdminManager.describeConfigs returns no config when 2+ config

[jira] [Updated] (KAFKA-12341) Duplicate javassist library found in broker classpath

[ https://issues.apache.org/jira/browse/KAFKA-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12341: Fix Version/s: (was: 2.7.1) 2.8.0 > Duplicate javassist library found in br

[jira] [Commented] (KAFKA-12341) Duplicate javassist library found in broker classpath

[ https://issues.apache.org/jira/browse/KAFKA-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289082#comment-17289082 ] Ismael Juma commented on KAFKA-12341: - Thanks for the PR. Submitted a fix here:  htt

[jira] [Assigned] (KAFKA-12341) Duplicate javassist library found in broker classpath

[ https://issues.apache.org/jira/browse/KAFKA-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-12341: --- Assignee: Ismael Juma > Duplicate javassist library found in broker classpath > ---

[jira] [Commented] (KAFKA-12358) Migrate to Java 11

[ https://issues.apache.org/jira/browse/KAFKA-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288432#comment-17288432 ] Ismael Juma commented on KAFKA-12358: - Requiring Java 11 is a major decision and req

[jira] [Updated] (KAFKA-12357) Do not inline methods from the scala package by default

[ https://issues.apache.org/jira/browse/KAFKA-12357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12357: Fix Version/s: 2.8.0 > Do not inline methods from the scala package by default > -

[jira] [Created] (KAFKA-12357) Do not inline methods from the scala package by default

Ismael Juma created KAFKA-12357: --- Summary: Do not inline methods from the scala package by default Key: KAFKA-12357 URL: https://issues.apache.org/jira/browse/KAFKA-12357 Project: Kafka Issue T

[jira] [Commented] (KAFKA-12351) Fix misleading max.request.size behavior

[ https://issues.apache.org/jira/browse/KAFKA-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287768#comment-17287768 ] Ismael Juma commented on KAFKA-12351: - I think we have an existing JIRA about this b

[jira] [Commented] (KAFKA-3702) SslTransportLayer.close() does not shutdown gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285220#comment-17285220 ] Ismael Juma commented on KAFKA-3702: [~purplefox] it may be simplest if you submit a

[jira] [Commented] (KAFKA-3702) SslTransportLayer.close() does not shutdown gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285218#comment-17285218 ] Ismael Juma commented on KAFKA-3702: Also `isOutboundDone` says: {quote}Returns wheth

[jira] [Commented] (KAFKA-3702) SslTransportLayer.close() does not shutdown gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285215#comment-17285215 ] Ismael Juma commented on KAFKA-3702: [~purplefox] The documentation for `closeOutboun

[jira] [Commented] (KAFKA-3702) SslTransportLayer.close() does not shutdown gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285199#comment-17285199 ] Ismael Juma commented on KAFKA-3702: A possible issue (identified by [~david.mao]) is

[jira] [Commented] (KAFKA-12325) Is Kafka affected by Scala security vulnerability (CVE-2017-15288)?

[ https://issues.apache.org/jira/browse/KAFKA-12325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284438#comment-17284438 ] Ismael Juma commented on KAFKA-12325: - [~jrstacy] The scala library and reflect are

[jira] [Commented] (KAFKA-8629) Kafka Streams Apps to support small native images through GraalVM

[ https://issues.apache.org/jira/browse/KAFKA-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284437#comment-17284437 ] Ismael Juma commented on KAFKA-8629: KAFKA-12327 addresses one of the issues. I would

[jira] [Updated] (KAFKA-7025) Android client support

[ https://issues.apache.org/jira/browse/KAFKA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7025: --- Fix Version/s: 2.8.0 > Android client support > -- > > Key: KAFKA

[jira] [Commented] (KAFKA-7025) Android client support

[ https://issues.apache.org/jira/browse/KAFKA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284436#comment-17284436 ] Ismael Juma commented on KAFKA-7025: KAFKA-12327 will be part of Apache Kafka 2.8. Ho

[jira] [Updated] (KAFKA-12327) Remove MethodHandle usage in CompressionType

[ https://issues.apache.org/jira/browse/KAFKA-12327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12327: Fix Version/s: 2.8.0 > Remove MethodHandle usage in CompressionType >

[jira] [Commented] (KAFKA-7025) Android client support

[ https://issues.apache.org/jira/browse/KAFKA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284234#comment-17284234 ] Ismael Juma commented on KAFKA-7025: I submitted a PR that removes method handle usag

[jira] [Created] (KAFKA-12327) Remove MethodHandle usage in CompressionType

Ismael Juma created KAFKA-12327: --- Summary: Remove MethodHandle usage in CompressionType Key: KAFKA-12327 URL: https://issues.apache.org/jira/browse/KAFKA-12327 Project: Kafka Issue Type: Improv

[jira] [Assigned] (KAFKA-7025) Android client support

[ https://issues.apache.org/jira/browse/KAFKA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-7025: -- Assignee: (was: Ismael Juma) > Android client support > -- > >

[jira] [Assigned] (KAFKA-7025) Android client support

[ https://issues.apache.org/jira/browse/KAFKA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-7025: -- Assignee: Ismael Juma > Android client support > -- > > Ke

[jira] [Resolved] (KAFKA-12310) Update zookeeper to 3.5.9

[ https://issues.apache.org/jira/browse/KAFKA-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-12310. - Resolution: Fixed > Update zookeeper to 3.5.9 > - > > Ke

[jira] [Updated] (KAFKA-12310) Update zookeeper to 3.5.9

[ https://issues.apache.org/jira/browse/KAFKA-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12310: Fix Version/s: 2.4.2 > Update zookeeper to 3.5.9 > - > > K

[jira] [Updated] (KAFKA-12310) Update zookeeper to 3.5.9

[ https://issues.apache.org/jira/browse/KAFKA-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12310: Fix Version/s: 2.6.2 2.7.1 2.8.0 2.5.2 >

[jira] [Commented] (KAFKA-12310) Update zookeeper to 3.5.9

[ https://issues.apache.org/jira/browse/KAFKA-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280695#comment-17280695 ] Ismael Juma commented on KAFKA-12310: - PR: https://github.com/apache/kafka/pull/9977

[jira] [Created] (KAFKA-12310) Update zookeeper to 3.5.9

Ismael Juma created KAFKA-12310: --- Summary: Update zookeeper to 3.5.9 Key: KAFKA-12310 URL: https://issues.apache.org/jira/browse/KAFKA-12310 Project: Kafka Issue Type: Improvement R

[jira] [Commented] (KAFKA-12179) Install Kafka on IBM Cloud

[ https://issues.apache.org/jira/browse/KAFKA-12179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271174#comment-17271174 ] Ismael Juma commented on KAFKA-12179: - Hi. I am not sure what is expected from this

[jira] [Commented] (KAFKA-12164) ssue when kafka connect worker pod restart, during creation of nested partition directories in hdfs file system.

[ https://issues.apache.org/jira/browse/KAFKA-12164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268580#comment-17268580 ] Ismael Juma commented on KAFKA-12164: - cc [~kkonstantine] [~rhauch] > ssue when kaf

[jira] [Commented] (KAFKA-12227) Return CompletableFuture from KafkaProducer.send

[ https://issues.apache.org/jira/browse/KAFKA-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268577#comment-17268577 ] Ismael Juma commented on KAFKA-12227: - [~chia7712] Feel free to take over if you hav

[jira] [Commented] (KAFKA-12207) Do not maintain list of latest producer append information

[ https://issues.apache.org/jira/browse/KAFKA-12207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267758#comment-17267758 ] Ismael Juma commented on KAFKA-12207: - {quote}document that if the offset is require

[jira] [Resolved] (KAFKA-10841) LogReadResult should be able to converted to FetchPartitionData

[ https://issues.apache.org/jira/browse/KAFKA-10841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-10841. - Fix Version/s: 2.8.0 Resolution: Fixed > LogReadResult should be able to converted to Fet

[jira] [Commented] (KAFKA-12220) Replace PowerMock by Mockito

[ https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267409#comment-17267409 ] Ismael Juma commented on KAFKA-12220: - One question: are we replacing `PowerMock` an

[jira] [Commented] (KAFKA-12220) Replace PowerMock by Mockito

[ https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267406#comment-17267406 ] Ismael Juma commented on KAFKA-12220: - Also, I would start with `streams` since ther

[jira] [Commented] (KAFKA-12220) Replace PowerMock by Mockito

[ https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267405#comment-17267405 ] Ismael Juma commented on KAFKA-12220: - That doesn't seem too bad, I would do one PR

[jira] [Commented] (KAFKA-12220) Replace PowerMock by Mockito

[ https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267142#comment-17267142 ] Ismael Juma commented on KAFKA-12220: - I think that will result in too many PRs. How

[jira] [Commented] (KAFKA-12175) Migrate generator module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266984#comment-17266984 ] Ismael Juma commented on KAFKA-12175: - [~Bertber] Are you going to submit a PR soon?

[jira] [Resolved] (KAFKA-7343) Migrate connect modules to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7343. Resolution: Duplicate Marking as duplicate since tickets have been filed for all connect modules.

[jira] [Resolved] (KAFKA-12202) Migrate connect:mirror module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-12202. - Fix Version/s: 2.8.0 Resolution: Fixed > Migrate connect:mirror module to JUnit 5 > -

[jira] [Resolved] (KAFKA-12201) Migrate connect:basic-auth-extension module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-12201. - Fix Version/s: 2.8.0 Resolution: Fixed > Migrate connect:basic-auth-extension module to J

[jira] [Updated] (KAFKA-12201) Migrate connect:basic-auth-extension module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12201: Summary: Migrate connect:basic-auth-extension module to JUnit 5 (was: Migrate connect:basic-auth-

[jira] [Comment Edited] (KAFKA-12199) Migrate connect:runtime module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266032#comment-17266032 ] Ismael Juma edited comment on KAFKA-12199 at 1/18/21, 1:07 AM: ---

[jira] [Updated] (KAFKA-12200) Migrate connect:file module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-12200: Fix Version/s: 2.8.0 > Migrate connect:file module to JUnit 5 > --

[jira] [Resolved] (KAFKA-12200) Migrate connect:file module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-12200. - Resolution: Fixed > Migrate connect:file module to JUnit 5 > ---

[jira] [Commented] (KAFKA-12216) Improve flaky test reporting

[ https://issues.apache.org/jira/browse/KAFKA-12216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266913#comment-17266913 ] Ismael Juma commented on KAFKA-12216: - {quote}[https://github.com/jenkinsci/junit-pl

[jira] [Created] (KAFKA-12216) Improve flaky test reporting

Ismael Juma created KAFKA-12216: --- Summary: Improve flaky test reporting Key: KAFKA-12216 URL: https://issues.apache.org/jira/browse/KAFKA-12216 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-12199) Migrate connect:runtime module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266032#comment-17266032 ] Ismael Juma commented on KAFKA-12199: - We have already picked Mockito as our mocking

[jira] [Commented] (KAFKA-10877) Instantiating loggers for every FetchContext causes low request handler idle pool ratio.

[ https://issues.apache.org/jira/browse/KAFKA-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265009#comment-17265009 ] Ismael Juma commented on KAFKA-10877: - Sounds good. > Instantiating loggers for eve

[jira] [Commented] (KAFKA-10877) Instantiating loggers for every FetchContext causes low request handler idle pool ratio.

[ https://issues.apache.org/jira/browse/KAFKA-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264933#comment-17264933 ] Ismael Juma commented on KAFKA-10877: - [~smccauliff] Any update on the PR? > Instan

[jira] [Assigned] (KAFKA-12201) Migrate connect:basic-auth-extensio module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-12201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-12201: --- Assignee: Ismael Juma > Migrate connect:basic-auth-extensio module to JUnit 5 > ---

[jira] [Commented] (KAFKA-7343) Migrate connect modules to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264651#comment-17264651 ] Ismael Juma commented on KAFKA-7343: It probably makes sense to have multiple tickets

[jira] [Resolved] (KAFKA-7340) Migrate clients module to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7340. Fix Version/s: 2.8.0 Resolution: Fixed > Migrate clients module to JUnit 5 > ---

[jira] [Assigned] (KAFKA-7343) Migrate connect modules to JUnit 5

[ https://issues.apache.org/jira/browse/KAFKA-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-7343: -- Assignee: (was: Ismael Juma) > Migrate connect modules to JUnit 5 > --

[jira] [Commented] (KAFKA-10206) Admin can transiently return incorrect results about topics

[ https://issues.apache.org/jira/browse/KAFKA-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257114#comment-17257114 ] Ismael Juma commented on KAFKA-10206: - One thing to keep in mind is that the quorum

[jira] [Commented] (KAFKA-10694) Implement zero copy for FetchSnapshot

[ https://issues.apache.org/jira/browse/KAFKA-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255171#comment-17255171 ] Ismael Juma commented on KAFKA-10694: - Can we not use SendBuilder? > Implement zero

[jira] [Commented] (KAFKA-10877) Instantiating loggers for every FetchContext causes low request handler idle pool ratio.

[ https://issues.apache.org/jira/browse/KAFKA-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253155#comment-17253155 ] Ismael Juma commented on KAFKA-10877: - {quote}  It's not clear if there are other pl

[jira] [Commented] (KAFKA-10877) Instantiating loggers for every FetchContext causes low request handler idle pool ratio.

[ https://issues.apache.org/jira/browse/KAFKA-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253153#comment-17253153 ] Ismael Juma commented on KAFKA-10877: - [~smccauliff] Kafka uses log4j 1 by default,

[jira] [Commented] (KAFKA-10877) Instantiating loggers for every FetchContext causes low request handler idle pool ratio.

[ https://issues.apache.org/jira/browse/KAFKA-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253149#comment-17253149 ] Ismael Juma commented on KAFKA-10877: - Thanks [~smccauliff]. Do you intend to submit

[jira] [Resolved] (KAFKA-10852) AlterIsr should not be throttled

[ https://issues.apache.org/jira/browse/KAFKA-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-10852. - Fix Version/s: 2.7.1 2.8.0 Resolution: Fixed > AlterIsr should not be

[jira] [Updated] (KAFKA-10852) AlterIsr should not be throttled

[ https://issues.apache.org/jira/browse/KAFKA-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-10852: Summary: AlterIsr should not be throttled (was: AlterIsr should be a cluster action) > AlterIsr

[jira] [Created] (KAFKA-10852) AlterIsr should be a cluster action

Ismael Juma created KAFKA-10852: --- Summary: AlterIsr should be a cluster action Key: KAFKA-10852 URL: https://issues.apache.org/jira/browse/KAFKA-10852 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-10802) Spurious log message when starting consumers

[ https://issues.apache.org/jira/browse/KAFKA-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247490#comment-17247490 ] Ismael Juma commented on KAFKA-10802: - Thanks [~mimaison]! > Spurious log message w

[jira] [Commented] (KAFKA-10827) Consumer group coordinator node never gets updated for manual partition assignment with infrequent requests

[ https://issues.apache.org/jira/browse/KAFKA-10827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246558#comment-17246558 ] Ismael Juma commented on KAFKA-10827: - cc [~ableegoldman] and [~guozhang] who were l

[jira] [Commented] (KAFKA-10802) Spurious log message when starting consumers

[ https://issues.apache.org/jira/browse/KAFKA-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246229#comment-17246229 ] Ismael Juma commented on KAFKA-10802: - Why can't we backport the fix to 2.7 and 2.6?

[jira] [Resolved] (KAFKA-10818) Skip conversion to `Struct` when serializing generated requests/responses

[ https://issues.apache.org/jira/browse/KAFKA-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-10818. - Resolution: Fixed > Skip conversion to `Struct` when serializing generated requests/responses >

[jira] [Updated] (KAFKA-10818) Skip conversion to `Struct` when serializing generated requests/responses

[ https://issues.apache.org/jira/browse/KAFKA-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-10818: Fix Version/s: 2.8.0 > Skip conversion to `Struct` when serializing generated requests/responses >

[jira] [Created] (KAFKA-10818) Skip conversion to `Struct` when serializing generated requests/responses

Ismael Juma created KAFKA-10818: --- Summary: Skip conversion to `Struct` when serializing generated requests/responses Key: KAFKA-10818 URL: https://issues.apache.org/jira/browse/KAFKA-10818 Project: Kafk

[jira] [Commented] (KAFKA-6689) Kafka not release .deleted file.

[ https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244875#comment-17244875 ] Ismael Juma commented on KAFKA-6689: No, that's not expected. If you are seeing diffe

[jira] [Commented] (KAFKA-7588) Rationalize configurations passed to pluggable APIs

[ https://issues.apache.org/jira/browse/KAFKA-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243261#comment-17243261 ] Ismael Juma commented on KAFKA-7588: Seems like the PR was merged, so this Jira shoul

[jira] [Commented] (KAFKA-10776) JMX metric RequestsPerSec requires API version to access

[ https://issues.apache.org/jira/browse/KAFKA-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240437#comment-17240437 ] Ismael Juma commented on KAFKA-10776: - See  https://cwiki.apache.org/confluence/disp

[jira] [Commented] (KAFKA-10717) ACL authorization log when consumer requires all topics

[ https://issues.apache.org/jira/browse/KAFKA-10717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231585#comment-17231585 ] Ismael Juma commented on KAFKA-10717: - Thanks for the report. Can you still see this

[jira] [Resolved] (KAFKA-10469) Respect logging hierarchy (KIP-676)

[ https://issues.apache.org/jira/browse/KAFKA-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-10469. - Fix Version/s: 2.8.0 Resolution: Fixed > Respect logging hierarchy (KIP-676) > --

[jira] [Updated] (KAFKA-10469) Respect logging hierarchy (KIP-676)

[ https://issues.apache.org/jira/browse/KAFKA-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-10469: Summary: Respect logging hierarchy (KIP-676) (was: describeConfigs() for broker loggers returns i

[jira] [Commented] (KAFKA-10649) CPU increase after the upgrade to Kafka 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221296#comment-17221296 ] Ismael Juma commented on KAFKA-10649: - Thanks for the report. This is likely KAFKA-9

[jira] [Commented] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214294#comment-17214294 ] Ismael Juma commented on KAFKA-10613: - When did we regress here? > Broker should no

[jira] [Commented] (KAFKA-9915) Throttle Create Topic, Create Partition and Delete Topic Operations

[ https://issues.apache.org/jira/browse/KAFKA-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214121#comment-17214121 ] Ismael Juma commented on KAFKA-9915: [~dajac] Sounds good, I missed it when I was loo

[jira] [Commented] (KAFKA-10606) Auto create non-existent topics when fetching metadata for all topics

[ https://issues.apache.org/jira/browse/KAFKA-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214077#comment-17214077 ] Ismael Juma commented on KAFKA-10606: - Seems like the way to fix this is to pass `fa

[jira] [Comment Edited] (KAFKA-10606) Auto create non-existent topics when fetching metadata for all topics

[ https://issues.apache.org/jira/browse/KAFKA-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214077#comment-17214077 ] Ismael Juma edited comment on KAFKA-10606 at 10/14/20, 5:19 PM: --

<    2   3   4   5   6   7   8   9   10   11   >