[jira] [Updated] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6042: --- Affects Version/s: (was: 1.0.0) > Kafka Request Handler deadlocks and brings down the cluster. >

[jira] [Commented] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803630#comment-16803630 ] Ismael Juma commented on KAFKA-6042: Fixed. > Kafka Request Handler deadlocks and br

[jira] [Commented] (KAFKA-8103) Kafka SIGSEGV on kafka-network-thread

[ https://issues.apache.org/jira/browse/KAFKA-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803955#comment-16803955 ] Ismael Juma commented on KAFKA-8103: Looks like a JVM JIT bug. I haven't seen this on

[jira] [Commented] (KAFKA-8182) IllegalStateException in NetworkClient.initiateConnect when handling UnknownHostException thrown from ClusterConnectionStates.connecting

[ https://issues.apache.org/jira/browse/KAFKA-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808773#comment-16808773 ] Ismael Juma commented on KAFKA-8182: Looks like a duplicate of KAFKA-7974. > Illegal

[jira] [Updated] (KAFKA-7974) KafkaAdminClient loses worker thread/enters zombie state when initial DNS lookup fails

[ https://issues.apache.org/jira/browse/KAFKA-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7974: --- Fix Version/s: 2.2.1 2.1.2 > KafkaAdminClient loses worker thread/enters zombie st

[jira] [Updated] (KAFKA-7974) KafkaAdminClient loses worker thread/enters zombie state when initial DNS lookup fails

[ https://issues.apache.org/jira/browse/KAFKA-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7974: --- Affects Version/s: 2.2.0 2.1.1 > KafkaAdminClient loses worker thread/enters z

[jira] [Commented] (KAFKA-8182) IllegalStateException in NetworkClient.initiateConnect when handling UnknownHostException thrown from ClusterConnectionStates.connecting

[ https://issues.apache.org/jira/browse/KAFKA-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808840#comment-16808840 ] Ismael Juma commented on KAFKA-8182: Yes. > IllegalStateException in NetworkClient.i

[jira] [Commented] (KAFKA-8151) Broker hangs and lockups after Zookeeper outages

[ https://issues.apache.org/jira/browse/KAFKA-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811711#comment-16811711 ] Ismael Juma commented on KAFKA-8151: [~jammann] Interesting that the problem went awa

[jira] [Commented] (KAFKA-8151) Broker hangs and lockups after Zookeeper outages

[ https://issues.apache.org/jira/browse/KAFKA-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811895#comment-16811895 ] Ismael Juma commented on KAFKA-8151: Thank you so much for the detail. This is very h

[jira] [Updated] (KAFKA-8134) ProducerConfig.LINGER_MS_CONFIG undocumented breaking change in kafka-clients 2.1

[ https://issues.apache.org/jira/browse/KAFKA-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8134: --- Fix Version/s: 2.2.1 2.1.2 2.3.0 > ProducerConfig.LINGER_MS_CON

[jira] [Commented] (KAFKA-8230) Add static membership support in librd consumer client

[ https://issues.apache.org/jira/browse/KAFKA-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817148#comment-16817148 ] Ismael Juma commented on KAFKA-8230: That's a good idea, but we should track it via

[jira] [Created] (KAFKA-8316) Remove deprecated usage of Slf4jRequestLog, SslContextFactory

Ismael Juma created KAFKA-8316: -- Summary: Remove deprecated usage of Slf4jRequestLog, SslContextFactory Key: KAFKA-8316 URL: https://issues.apache.org/jira/browse/KAFKA-8316 Project: Kafka Issu

[jira] [Resolved] (KAFKA-8308) Update jetty for security vulnerability CVE-2019-10241

[ https://issues.apache.org/jira/browse/KAFKA-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8308. Resolution: Fixed Assignee: Ismael Juma (was: Lee Dongjin) Fix Version/s: 2.3.0 Th

[jira] [Commented] (KAFKA-7954) When broker IP addresses change client never resolves new addresses to fetch metadata

[ https://issues.apache.org/jira/browse/KAFKA-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833450#comment-16833450 ] Ismael Juma commented on KAFKA-7954: [~rpo...@gmail.com] See my question above, have

[jira] [Updated] (KAFKA-8332) Regression in handling of JoinGroupRequest disallows deterministic protocol selection based on order of preference

[ https://issues.apache.org/jira/browse/KAFKA-8332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8332: --- Fix Version/s: 2.3.0 > Regression in handling of JoinGroupRequest disallows deterministic protocol >

[jira] [Commented] (KAFKA-8359) Reconsider default for leader imbalance percentage

[ https://issues.apache.org/jira/browse/KAFKA-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840483#comment-16840483 ] Ismael Juma commented on KAFKA-8359: There is no good reason for the existing default

[jira] [Resolved] (KAFKA-8422) Client should not use old versions of OffsetsForLeaderEpoch

[ https://issues.apache.org/jira/browse/KAFKA-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8422. Resolution: Fixed > Client should not use old versions of OffsetsForLeaderEpoch > -

[jira] [Closed] (KAFKA-7730) Limit total number of active connections in the broker

[ https://issues.apache.org/jira/browse/KAFKA-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma closed KAFKA-7730. -- > Limit total number of active connections in the broker >

[jira] [Closed] (KAFKA-7719) Improve fairness in SocketServer processors

[ https://issues.apache.org/jira/browse/KAFKA-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma closed KAFKA-7719. -- > Improve fairness in SocketServer processors > --- > >

[jira] [Resolved] (KAFKA-7321) ensure timely processing of deletion requests in Kafka topic (Time-based log compaction)

[ https://issues.apache.org/jira/browse/KAFKA-7321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7321. Resolution: Fixed Fix Version/s: 2.3.0 This was merged some time ago and will be in 2.3.0.

[jira] [Commented] (KAFKA-8448) Too many kafka.log.Log instances (Memory Leak)

[ https://issues.apache.org/jira/browse/KAFKA-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852041#comment-16852041 ] Ismael Juma commented on KAFKA-8448: Nice find, thanks for the report. > Too many ka

[jira] [Commented] (KAFKA-8404) Authorization header is not passed in Connect when forwarding REST requests

[ https://issues.apache.org/jira/browse/KAFKA-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854712#comment-16854712 ] Ismael Juma commented on KAFKA-8404: [~rhauch] Is this an actual blocker for the 2.3

[jira] [Commented] (KAFKA-8272) Changed(De)Serializer does not forward configure() call

[ https://issues.apache.org/jira/browse/KAFKA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854713#comment-16854713 ] Ismael Juma commented on KAFKA-8272: [~mjsax] Are you still targeting 2.3.0? Only blo

[jira] [Created] (KAFKA-8471) Replace control requests/responses with automated protocol

Ismael Juma created KAFKA-8471: -- Summary: Replace control requests/responses with automated protocol Key: KAFKA-8471 URL: https://issues.apache.org/jira/browse/KAFKA-8471 Project: Kafka Issue Ty

[jira] [Commented] (KAFKA-8507) Support --bootstrap-server in all command line tools

[ https://issues.apache.org/jira/browse/KAFKA-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858904#comment-16858904 ] Ismael Juma commented on KAFKA-8507: There's a PR for this. > Support --bootstrap-se

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16859536#comment-16859536 ] Ismael Juma commented on KAFKA-8514: Thanks for filing this, I had also noticed this

[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 com

[jira] [Updated] (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 updated KAFKA-8514: --- Fix Version/s: (was: 2.3.0) 2.4.0 > Kafka clients should not include Scala's J

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

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

[jira] [Created] (KAFKA-8544) Remove legacy kafka.admin.AdminClient

Ismael Juma created KAFKA-8544: -- Summary: Remove legacy kafka.admin.AdminClient Key: KAFKA-8544 URL: https://issues.apache.org/jira/browse/KAFKA-8544 Project: Kafka Issue Type: Bug R

[jira] [Updated] (KAFKA-8544) Remove legacy kafka.admin.AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8544: --- Issue Type: New Feature (was: Bug) > Remove legacy kafka.admin.AdminClient > ---

[jira] [Created] (KAFKA-8545) Remove legacy ZkUtils

Ismael Juma created KAFKA-8545: -- Summary: Remove legacy ZkUtils Key: KAFKA-8545 URL: https://issues.apache.org/jira/browse/KAFKA-8545 Project: Kafka Issue Type: Bug Reporter: Ismael

[jira] [Updated] (KAFKA-8545) Remove legacy ZkUtils

[ https://issues.apache.org/jira/browse/KAFKA-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8545: --- Issue Type: Improvement (was: Bug) > Remove legacy ZkUtils > - > >

[jira] [Updated] (KAFKA-8544) Remove legacy kafka.admin.AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8544: --- Issue Type: Improvement (was: New Feature) > Remove legacy kafka.admin.AdminClient > ---

[jira] [Resolved] (KAFKA-8559) PartitionStates.partitionStates cause array grow allocation.

[ https://issues.apache.org/jira/browse/KAFKA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8559. Resolution: Fixed Fix Version/s: 2.4.0 > PartitionStates.partitionStates cause array grow al

[jira] [Updated] (KAFKA-5723) Refactor BrokerApiVersionsCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5723: --- Description: Currently it uses the deprecated AdminClient and in order to remove usages of that clie

[jira] [Resolved] (KAFKA-8563) Minor: Remove method call in networkSend. Rely on java's vargs boxing/autoboxing

[ https://issues.apache.org/jira/browse/KAFKA-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8563. Resolution: Fixed Fix Version/s: 2.4.0 > Minor: Remove method call in networkSend. Rely on j

[jira] [Updated] (KAFKA-7197) Support Scala 2.13.0

[ https://issues.apache.org/jira/browse/KAFKA-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7197: --- Fix Version/s: 2.4.0 > Support Scala 2.13.0 > > > Key: KAFKA-719

[jira] [Resolved] (KAFKA-7197) Support Scala 2.13.0

[ https://issues.apache.org/jira/browse/KAFKA-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7197. Resolution: Fixed > Support Scala 2.13.0 > > > Key: KAFKA-7197

[jira] [Updated] (KAFKA-7197) Support Scala 2.13.0

[ https://issues.apache.org/jira/browse/KAFKA-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7197: --- Summary: Support Scala 2.13.0 (was: Release a milestone build for Scala 2.13.0 M3) > Support Scala

[jira] [Updated] (KAFKA-7197) Support Scala 2.13.0

[ https://issues.apache.org/jira/browse/KAFKA-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7197: --- Description: Scala 2.13.0 has been released, we should support it. (was: Releasing a milestone versi

[jira] [Updated] (KAFKA-7197) Support Scala 2.13.0

[ https://issues.apache.org/jira/browse/KAFKA-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7197: --- Priority: Major (was: Minor) > Support Scala 2.13.0 > > > Key:

[jira] [Resolved] (KAFKA-8545) Remove legacy ZkUtils

[ https://issues.apache.org/jira/browse/KAFKA-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8545. Resolution: Fixed > Remove legacy ZkUtils > - > > Key: KAFKA-85

[jira] [Created] (KAFKA-8634) Update ZooKeeper to 3.5.5

Ismael Juma created KAFKA-8634: -- Summary: Update ZooKeeper to 3.5.5 Key: KAFKA-8634 URL: https://issues.apache.org/jira/browse/KAFKA-8634 Project: Kafka Issue Type: Improvement Repor

[jira] [Resolved] (KAFKA-7178) Is kafka compatible with zookeeper 3.5.x ?

[ https://issues.apache.org/jira/browse/KAFKA-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7178. Resolution: Duplicate KAFKA-8634 tracks updating to ZK 3.5.x. > Is kafka compatible with zookeeper

[jira] [Updated] (KAFKA-8634) Update ZooKeeper to 3.5.5

[ https://issues.apache.org/jira/browse/KAFKA-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8634: --- Fix Version/s: 2.4.0 > Update ZooKeeper to 3.5.5 > - > > Key:

[jira] [Commented] (KAFKA-8635) Unnecessary wait when looking up coordinator before transactional request

[ https://issues.apache.org/jira/browse/KAFKA-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880162#comment-16880162 ] Ismael Juma commented on KAFKA-8635: Nice investigation, thanks for the report. cc [~

[jira] [Commented] (KAFKA-8684) Create a test of consumer group behavior that tests old clients and new servers

[ https://issues.apache.org/jira/browse/KAFKA-8684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888313#comment-16888313 ] Ismael Juma commented on KAFKA-8684: We have tests for individual protocols. In any c

[jira] [Updated] (KAFKA-9261) NPE when updating client metadata

[ https://issues.apache.org/jira/browse/KAFKA-9261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9261: --- Fix Version/s: 2.3.2 2.4.0 > NPE when updating client metadata > -

[jira] [Updated] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is invalid

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6266: --- Fix Version/s: 2.4.1 2.5.0 > Kafka 1.0.0 : Repeated occurrence of WARN Resetting f

[jira] [Resolved] (KAFKA-9265) kafka.log.Log instances are leaking on log delete

[ https://issues.apache.org/jira/browse/KAFKA-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9265. Fix Version/s: 2.3.2 2.4.0 Resolution: Fixed > kafka.log.Log instances ar

[jira] [Commented] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988460#comment-16988460 ] Ismael Juma commented on KAFKA-9268: Is there any reason why people would not upgrade

[jira] [Updated] (KAFKA-9232) Coordinator new member heartbeat completion does not work for JoinGroup v3

[ https://issues.apache.org/jira/browse/KAFKA-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9232: --- Affects Version/s: 2.3.1 2.1.1 2.2.2 > Coordinator new

[jira] [Updated] (KAFKA-9212) Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest

[ https://issues.apache.org/jira/browse/KAFKA-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9212: --- Affects Version/s: (was: 2.3.2) (was: 2.4.0) 2.3

[jira] [Updated] (KAFKA-9212) Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest

[ https://issues.apache.org/jira/browse/KAFKA-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9212: --- Priority: Blocker (was: Critical) > Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetReque

[jira] [Updated] (KAFKA-9212) Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest

[ https://issues.apache.org/jira/browse/KAFKA-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9212: --- Fix Version/s: 2.3.2 2.4.0 > Keep receiving FENCED_LEADER_EPOCH while sending List

[jira] [Resolved] (KAFKA-9212) Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest

[ https://issues.apache.org/jira/browse/KAFKA-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9212. Resolution: Fixed > Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest > --

[jira] [Created] (KAFKA-9324) Drop support for Scala 2.11 (KIP-531)

Ismael Juma created KAFKA-9324: -- Summary: Drop support for Scala 2.11 (KIP-531) Key: KAFKA-9324 URL: https://issues.apache.org/jira/browse/KAFKA-9324 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-7267) KafkaStreams Scala DSL process method should accept a ProcessorSupplier

[ https://issues.apache.org/jira/browse/KAFKA-7267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001825#comment-17001825 ] Ismael Juma commented on KAFKA-7267: For what it's worth, we're planning to drop supp

[jira] [Created] (KAFKA-9333) Shim `core` module that targets default scala version (KIP-531)

Ismael Juma created KAFKA-9333: -- Summary: Shim `core` module that targets default scala version (KIP-531) Key: KAFKA-9333 URL: https://issues.apache.org/jira/browse/KAFKA-9333 Project: Kafka Is

[jira] [Commented] (KAFKA-9338) Incremental fetch sessions do not maintain or use leader epoch for fencing purposes

[ https://issues.apache.org/jira/browse/KAFKA-9338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004309#comment-17004309 ] Ismael Juma commented on KAFKA-9338: Cc [~hachikuji] [~cmccabe] > Incremental fetch

[jira] [Commented] (KAFKA-9339) Increased CPU utilization in brokers in 2.4.0

[ https://issues.apache.org/jira/browse/KAFKA-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004407#comment-17004407 ] Ismael Juma commented on KAFKA-9339: OpenJDK 11 includes Flight Recorder and generall

[jira] [Commented] (KAFKA-9011) Add KStream#flatTransform and KStream#flatTransformValues to Scala API

[ https://issues.apache.org/jira/browse/KAFKA-9011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004684#comment-17004684 ] Ismael Juma commented on KAFKA-9011: Yeah, public APIs can only be added in feature r

[jira] [Updated] (KAFKA-3061) Get rid of Guava dependency

[ https://issues.apache.org/jira/browse/KAFKA-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3061: --- Fix Version/s: 2.5.0 > Get rid of Guava dependency > --- > >

[jira] [Assigned] (KAFKA-3061) Get rid of Guava dependency

[ https://issues.apache.org/jira/browse/KAFKA-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3061: -- Assignee: Ismael Juma (was: Rekha Joshi) > Get rid of Guava dependency >

[jira] [Updated] (KAFKA-8959) Update Guava to 24 (or newer) or remove dependency

[ https://issues.apache.org/jira/browse/KAFKA-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8959: --- Fix Version/s: (was: 2.5.0) > Update Guava to 24 (or newer) or remove dependency > --

[jira] [Resolved] (KAFKA-8959) Update Guava to 24 (or newer) or remove dependency

[ https://issues.apache.org/jira/browse/KAFKA-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8959. Resolution: Duplicate Marking this as a duplicate of KAFKA-3061 since the newest version of reflec

[jira] [Commented] (KAFKA-3061) Get rid of Guava dependency

[ https://issues.apache.org/jira/browse/KAFKA-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010692#comment-17010692 ] Ismael Juma commented on KAFKA-3061: Reflections 0.9.12 no longer depends on Guava.

[jira] [Commented] (KAFKA-8477) Cannot consume and request metadata for __consumer_offsets topic in Kafka 2.2

[ https://issues.apache.org/jira/browse/KAFKA-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011553#comment-17011553 ] Ismael Juma commented on KAFKA-8477: Does this still happen with 2.4.0? There were so

[jira] [Commented] (KAFKA-9339) Increased CPU utilization in brokers in 2.4.0

[ https://issues.apache.org/jira/browse/KAFKA-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011751#comment-17011751 ] Ismael Juma commented on KAFKA-9339: No plans to drop support for Java 8 at the momen

[jira] [Resolved] (KAFKA-8786) Deprecated Gradle features making it incompatible with Gradle 6.0.

[ https://issues.apache.org/jira/browse/KAFKA-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8786. Fix Version/s: 2.5.0 Resolution: Fixed > Deprecated Gradle features making it incompatible w

[jira] [Commented] (KAFKA-9412) LogCleaner stopped for NoSuchElementException

[ https://issues.apache.org/jira/browse/KAFKA-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014365#comment-17014365 ] Ismael Juma commented on KAFKA-9412: Thanks for the report. 0.11.0.3 is very old. Wou

[jira] [Commented] (KAFKA-9403) Remove BaseConsumer from Mirrormaker

[ https://issues.apache.org/jira/browse/KAFKA-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014367#comment-17014367 ] Ismael Juma commented on KAFKA-9403: We can only remove this before a major new relea

[jira] [Updated] (KAFKA-9339) Increased CPU utilization in brokers in 2.4.0

[ https://issues.apache.org/jira/browse/KAFKA-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9339: --- Labels: performance (was: ) > Increased CPU utilization in brokers in 2.4.0 > --

[jira] [Commented] (KAFKA-9473) A large number of core system tests failing due to Kafka server failed to start on trunk

[ https://issues.apache.org/jira/browse/KAFKA-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023343#comment-17023343 ] Ismael Juma commented on KAFKA-9473: I think  [https://github.com/apache/kafka/commit

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

[ https://issues.apache.org/jira/browse/KAFKA-8531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023650#comment-17023650 ] Ismael Juma commented on KAFKA-8531: The default can only be used with new enough bro

[jira] [Commented] (KAFKA-9478) Controller may stop react on partition reassignment command in ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025265#comment-17025265 ] Ismael Juma commented on KAFKA-9478: Is this different than KAFKA-7854? > Controller

[jira] [Resolved] (KAFKA-7854) Behavior change in controller picking up partition reassignment tasks since 1.1.0

[ https://issues.apache.org/jira/browse/KAFKA-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7854. Resolution: Won't Fix I'm marking this as "Won't fix" since KIP-455 introduced a Kafka protocol API

[jira] [Commented] (KAFKA-9478) Controller may stop react on partition reassignment command in ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025771#comment-17025771 ] Ismael Juma commented on KAFKA-9478: Odd. cc [~hachikuji] to double check that there

[jira] [Resolved] (KAFKA-9026) Replace DescribeAcls request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9026. Fix Version/s: 2.5.0 Resolution: Fixed > Replace DescribeAcls request/response with automate

[jira] [Resolved] (KAFKA-9426) OffsetsForLeaderEpochClient Use Switch Statement

[ https://issues.apache.org/jira/browse/KAFKA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9426. Fix Version/s: 2.5.0 Resolution: Fixed > OffsetsForLeaderEpochClient Use Switch Statement >

[jira] [Resolved] (KAFKA-9405) Use Map API computeIfAbsent Where Applicable

[ https://issues.apache.org/jira/browse/KAFKA-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9405. Fix Version/s: 2.5.0 Resolution: Fixed > Use Map API computeIfAbsent Where Applicable >

[jira] [Resolved] (KAFKA-9408) Use StandardCharsets UTF-8 instead of UTF-8 Name

[ https://issues.apache.org/jira/browse/KAFKA-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9408. Fix Version/s: 2.5.0 Resolution: Fixed > Use StandardCharsets UTF-8 instead of UTF-8 Name >

[jira] [Resolved] (KAFKA-9474) Kafka RPC protocol should support type 'double'

[ https://issues.apache.org/jira/browse/KAFKA-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9474. Resolution: Fixed > Kafka RPC protocol should support type 'double' > -

[jira] [Updated] (KAFKA-9474) Kafka RPC protocol should support type 'double'

[ https://issues.apache.org/jira/browse/KAFKA-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9474: --- Fix Version/s: 2.5.0 > Kafka RPC protocol should support type 'double' >

[jira] [Updated] (KAFKA-8764) LogCleanerManager endless loop while compacting/cleaning segments

[ https://issues.apache.org/jira/browse/KAFKA-8764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-8764: --- Fix Version/s: 2.4.1 2.3.2 2.2.3 > LogCleanerManager endless lo

[jira] [Resolved] (KAFKA-9028) Replace DeleteAcls request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9028. Fix Version/s: 2.5.0 Assignee: Ismael Juma (was: Mickael Maison) Resolution: Fixed

[jira] [Resolved] (KAFKA-9027) Replace CreateAcls request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9027. Fix Version/s: 2.5.0 Assignee: Ismael Juma (was: Mickael Maison) Resolution: Fixed

[jira] [Resolved] (KAFKA-9491) Fast election during reassignment can lead to replica fetcher failures

[ https://issues.apache.org/jira/browse/KAFKA-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9491. Fix Version/s: 2.4.1 2.5.0 Resolution: Fixed > Fast election during reass

[jira] [Reopened] (KAFKA-9491) Fast election during reassignment can lead to replica fetcher failures

[ https://issues.apache.org/jira/browse/KAFKA-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-9491: Reopening as we are still considering a cherry-pick to 2.3. > Fast election during reassignment can le

[jira] [Commented] (KAFKA-8164) Improve test passing rate by rerunning flaky tests

[ https://issues.apache.org/jira/browse/KAFKA-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031153#comment-17031153 ] Ismael Juma commented on KAFKA-8164: We are doing this just for Jenkins PR builds, re

[jira] [Resolved] (KAFKA-8164) Improve test passing rate by rerunning flaky tests

[ https://issues.apache.org/jira/browse/KAFKA-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8164. Fix Version/s: 2.6.0 Resolution: Fixed > Improve test passing rate by rerunning flaky tests

[jira] [Created] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

Ismael Juma created KAFKA-9515: -- Summary: Upgrade ZooKeeper to 3.5.7 Key: KAFKA-9515 URL: https://issues.apache.org/jira/browse/KAFKA-9515 Project: Kafka Issue Type: Improvement Repo

[jira] [Updated] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-9515: --- Description: There are some critical fixes in ZK 3.5.7 and the first RC has been posted: [https://ma

[jira] [Commented] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031749#comment-17031749 ] Ismael Juma commented on KAFKA-9515: cc [~bbejeck] [~mumrah] > Upgrade ZooKeeper to

[jira] [Assigned] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-9515: -- Assignee: Ismael Juma > Upgrade ZooKeeper to 3.5.7 > -- > >

[jira] [Comment Edited] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033753#comment-17033753 ] Ismael Juma edited comment on KAFKA-9515 at 2/10/20 4:58 PM: -

[jira] [Commented] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033753#comment-17033753 ] Ismael Juma commented on KAFKA-9515: [~rndgstn] I actually think 2.5 should ship with

[jira] [Commented] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034526#comment-17034526 ] Ismael Juma commented on KAFKA-9515: Can we get the doc changes ready please? > Upgr

[jira] [Commented] (KAFKA-9504) Memory leak in KafkaMetrics registered to MBean

[ https://issues.apache.org/jira/browse/KAFKA-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035930#comment-17035930 ] Ismael Juma commented on KAFKA-9504: I believe this was fixed in the 2.4 branch (and

  1   2   3   4   5   6   7   8   9   10   >