[jira] [Resolved] (KAFKA-6088) Kafka Consumer slows down when reading from highly compacted topics

[ https://issues.apache.org/jira/browse/KAFKA-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6088. Resolution: Fixed Since it was fixed in 0.11.0.0, marking it as fixed. > Kafka Consumer slows down

[jira] [Reopened] (KAFKA-6088) Kafka Consumer slows down when reading from highly compacted topics

[ https://issues.apache.org/jira/browse/KAFKA-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-6088: > Kafka Consumer slows down when reading from highly compacted topics >

[jira] [Updated] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

[ https://issues.apache.org/jira/browse/KAFKA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6085: - Priority: Minor (was: Blocker) > Streams rebalancing may cause a first batch of fetched records t

[jira] [Resolved] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

[ https://issues.apache.org/jira/browse/KAFKA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6085. -- Resolution: Not A Problem Fix Version/s: (was: 1.0.0) This is actually not a bug, but

[jira] [Commented] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

[ https://issues.apache.org/jira/browse/KAFKA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210581#comment-16210581 ] ASF GitHub Bot commented on KAFKA-6085: --- Github user guozhangwang closed the pull re

[jira] [Commented] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

[ https://issues.apache.org/jira/browse/KAFKA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210580#comment-16210580 ] ASF GitHub Bot commented on KAFKA-6085: --- GitHub user guozhangwang reopened a pull re

[jira] [Commented] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

[ https://issues.apache.org/jira/browse/KAFKA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210579#comment-16210579 ] ASF GitHub Bot commented on KAFKA-6085: --- Github user guozhangwang closed the pull re

[jira] [Commented] (KAFKA-5140) Flaky ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210557#comment-16210557 ] ASF GitHub Bot commented on KAFKA-5140: --- GitHub user guozhangwang opened a pull requ

[jira] [Resolved] (KAFKA-6088) Kafka Consumer slows down when reading from highly compacted topics

[ https://issues.apache.org/jira/browse/KAFKA-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng resolved KAFKA-6088. Resolution: Won't Fix It is fixed in kafka client 0.11.0.0, and 0.11.0.0 clients can be used against

[jira] [Commented] (KAFKA-6088) Kafka Consumer slows down when reading from highly compacted topics

[ https://issues.apache.org/jira/browse/KAFKA-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210549#comment-16210549 ] James Cheng commented on KAFKA-6088: I spoke with Confluent engineers about this, and

[jira] [Created] (KAFKA-6088) Kafka Consumer slows down when reading from highly compacted topics

James Cheng created KAFKA-6088: -- Summary: Kafka Consumer slows down when reading from highly compacted topics Key: KAFKA-6088 URL: https://issues.apache.org/jira/browse/KAFKA-6088 Project: Kafka

[jira] [Commented] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

[ https://issues.apache.org/jira/browse/KAFKA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210527#comment-16210527 ] Ted Yu commented on KAFKA-6085: --- {code} final ConsumerRecords records = pollRequests

[jira] [Commented] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210519#comment-16210519 ] huxihx commented on KAFKA-6068: --- [~haiyangyu] Weird. Seem replication factor could only be i

[jira] [Commented] (KAFKA-6067) how to process when all isr crashed

[ https://issues.apache.org/jira/browse/KAFKA-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210475#comment-16210475 ] haiyangyu commented on KAFKA-6067: -- yes, when all rep in isr crashed , we lost the data o

[jira] [Commented] (KAFKA-6077) Let SimpleConsumer support Kerberos authentication

[ https://issues.apache.org/jira/browse/KAFKA-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210464#comment-16210464 ] huangjianan commented on KAFKA-6077: Thank you. This means SimpleConsumer is deprecate

[jira] [Commented] (KAFKA-6083) The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found.

[ https://issues.apache.org/jira/browse/KAFKA-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210435#comment-16210435 ] ASF GitHub Bot commented on KAFKA-6083: --- Github user efeg closed the pull request at

[jira] [Commented] (KAFKA-6083) The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found.

[ https://issues.apache.org/jira/browse/KAFKA-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210436#comment-16210436 ] ASF GitHub Bot commented on KAFKA-6083: --- GitHub user efeg reopened a pull request:

[jira] [Commented] (KAFKA-6083) The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found.

[ https://issues.apache.org/jira/browse/KAFKA-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210374#comment-16210374 ] ASF GitHub Bot commented on KAFKA-6083: --- GitHub user efeg opened a pull request:

[jira] [Commented] (KAFKA-6087) Scanning plugin.path needs to support relative symlinks

[ https://issues.apache.org/jira/browse/KAFKA-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210333#comment-16210333 ] ASF GitHub Bot commented on KAFKA-6087: --- GitHub user kkonstantine opened a pull requ

[jira] [Created] (KAFKA-6087) Scanning plugin.path needs to support relative symlinks

Konstantine Karantasis created KAFKA-6087: - Summary: Scanning plugin.path needs to support relative symlinks Key: KAFKA-6087 URL: https://issues.apache.org/jira/browse/KAFKA-6087 Project: Kafka

[jira] [Commented] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210323#comment-16210323 ] Vahid Hashemian commented on KAFKA-4682: I just started a KIP discussion for this

[jira] [Updated] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4682: --- Labels: kip (was: ) > Committed offsets should not be deleted if a consumer is still active >

[jira] [Assigned] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4682: -- Assignee: Vahid Hashemian > Committed offsets should not be deleted if a consumer is st

[jira] [Commented] (KAFKA-6086) KIP-210 Provide for custom error handling when Kafka Streams fails to produce

[ https://issues.apache.org/jira/browse/KAFKA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210296#comment-16210296 ] Matt Farmer commented on KAFKA-6086: Gotcha, it seemed like a few others had done it p

[jira] [Commented] (KAFKA-6086) KIP-210 Provide for custom error handling when Kafka Streams fails to produce

[ https://issues.apache.org/jira/browse/KAFKA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210291#comment-16210291 ] Ted Yu commented on KAFKA-6086: --- Normally there is no need to put the KIP number in the subj

[jira] [Created] (KAFKA-6086) KIP-210 Provide for custom error handling when Kafka Streams fails to produce

Matt Farmer created KAFKA-6086: -- Summary: KIP-210 Provide for custom error handling when Kafka Streams fails to produce Key: KAFKA-6086 URL: https://issues.apache.org/jira/browse/KAFKA-6086 Project: Kafk

[jira] [Updated] (KAFKA-6086) KIP-210 Provide for custom error handling when Kafka Streams fails to produce

[ https://issues.apache.org/jira/browse/KAFKA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Farmer updated KAFKA-6086: --- Labels: kip (was: ) > KIP-210 Provide for custom error handling when Kafka Streams fails to produce >

[jira] [Resolved] (KAFKA-5911) Avoid creation of extra Map for futures in KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved KAFKA-5911. --- Resolution: Later > Avoid creation of extra Map for futures in KafkaAdminClient >

[jira] [Created] (KAFKA-6085) Streams rebalancing may cause a first batch of fetched records to be dropped

Guozhang Wang created KAFKA-6085: Summary: Streams rebalancing may cause a first batch of fetched records to be dropped Key: KAFKA-6085 URL: https://issues.apache.org/jira/browse/KAFKA-6085 Project: K

[jira] [Resolved] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3083. Resolution: Fixed Assignee: Onur Karaman (was: Mayuresh Gharat) Fix Version/s: 1.1.0 This i

[jira] [Resolved] (KAFKA-3038) Speeding up partition reassignment after broker failure

[ https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3038. Resolution: Duplicate This is now fixed in KAFKA-5642. > Speeding up partition reassignment after broker fa

[jira] [Resolved] (KAFKA-4444) Aggregate requests sent from controller to broker during controlled shutdown

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-. Resolution: Duplicate This is now fixed in KAFKA-5642. > Aggregate requests sent from controller to broker

[jira] [Commented] (KAFKA-6084) ReassignPartitionsCommand should propagate JSON parsing failures

[ https://issues.apache.org/jira/browse/KAFKA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210101#comment-16210101 ] ASF GitHub Bot commented on KAFKA-6084: --- GitHub user viktorsomogyi opened a pull req

[jira] [Commented] (KAFKA-6084) ReassignPartitionsCommand should propagate JSON parsing failures

[ https://issues.apache.org/jira/browse/KAFKA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210100#comment-16210100 ] Ismael Juma commented on KAFKA-6084: It was done this way before we migrated to Jackso

[jira] [Created] (KAFKA-6084) ReassignPartitionsCommand should propagate JSON parsing failures

Viktor Somogyi created KAFKA-6084: - Summary: ReassignPartitionsCommand should propagate JSON parsing failures Key: KAFKA-6084 URL: https://issues.apache.org/jira/browse/KAFKA-6084 Project: Kafka

[jira] [Commented] (KAFKA-5836) Kafka Streams - API for specifying internal stream name on join

[ https://issues.apache.org/jira/browse/KAFKA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209955#comment-16209955 ] Guozhang Wang commented on KAFKA-5836: -- [~andy.chamb...@fundingcircle.com] Ah I under

[jira] [Assigned] (KAFKA-6083) The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found.

[ https://issues.apache.org/jira/browse/KAFKA-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-6083: --- Assignee: Adem Efe Gencer > The Fetcher should add the InvalidRecordException as a cause to t

[jira] [Created] (KAFKA-6083) The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found.

Jiangjie Qin created KAFKA-6083: --- Summary: The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found. Key: KAFKA-6083 URL: https://issues.apache.org/jira/browse/

[jira] [Commented] (KAFKA-6081) response error code checking

[ https://issues.apache.org/jira/browse/KAFKA-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209909#comment-16209909 ] Ismael Juma commented on KAFKA-6081: Perfect, thanks. > response error code checking

[jira] [Commented] (KAFKA-6081) response error code checking

[ https://issues.apache.org/jira/browse/KAFKA-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209903#comment-16209903 ] Onur Karaman commented on KAFKA-6081: - [~ijuma] There are some scenarios where we only

[jira] [Commented] (KAFKA-6081) response error code checking

[ https://issues.apache.org/jira/browse/KAFKA-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209861#comment-16209861 ] Ismael Juma commented on KAFKA-6081: Something to consider as well: should we check th

[jira] [Created] (KAFKA-6082) consider fencing zookeeper updates with controller epoch zkVersion

Onur Karaman created KAFKA-6082: --- Summary: consider fencing zookeeper updates with controller epoch zkVersion Key: KAFKA-6082 URL: https://issues.apache.org/jira/browse/KAFKA-6082 Project: Kafka

[jira] [Updated] (KAFKA-5029) cleanup javadocs and logging

[ https://issues.apache.org/jira/browse/KAFKA-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5029: Description: Remove state change logger, splitting it up into the controller logs or broker logs. >

[jira] [Created] (KAFKA-6081) response error code checking

Onur Karaman created KAFKA-6081: --- Summary: response error code checking Key: KAFKA-6081 URL: https://issues.apache.org/jira/browse/KAFKA-6081 Project: Kafka Issue Type: Sub-task Rep

[jira] [Updated] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-1120: Issue Type: Sub-task (was: Bug) Parent: KAFKA-5027 > Controller could miss a broker state c

[jira] [Updated] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

[ https://issues.apache.org/jira/browse/KAFKA-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-6029: Issue Type: Sub-task (was: Improvement) Parent: KAFKA-5027 > Controller should wait for the

[jira] [Resolved] (KAFKA-5083) always leave the last surviving member of the ISR in ZK

[ https://issues.apache.org/jira/browse/KAFKA-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5083. - Resolution: Fixed This has been fixed in KAFKA-5642. > always leave the last surviving member of

[jira] [Commented] (KAFKA-6071) Use ZookeeperClient in LogManager

[ https://issues.apache.org/jira/browse/KAFKA-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209796#comment-16209796 ] ASF GitHub Bot commented on KAFKA-6071: --- GitHub user omkreddy opened a pull request:

[jira] [Assigned] (KAFKA-6071) Use ZookeeperClient in LogManager

[ https://issues.apache.org/jira/browse/KAFKA-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6071: Assignee: Manikumar > Use ZookeeperClient in LogManager > -- > >

[jira] [Created] (KAFKA-6079) Idempotent production for source connectors

Antony Stubbs created KAFKA-6079: Summary: Idempotent production for source connectors Key: KAFKA-6079 URL: https://issues.apache.org/jira/browse/KAFKA-6079 Project: Kafka Issue Type: New Fea

[jira] [Created] (KAFKA-6080) Transactional EoS for source connectors

Antony Stubbs created KAFKA-6080: Summary: Transactional EoS for source connectors Key: KAFKA-6080 URL: https://issues.apache.org/jira/browse/KAFKA-6080 Project: Kafka Issue Type: New Feature

[jira] [Assigned] (KAFKA-6051) ReplicaFetcherThread should close the ReplicaFetcherBlockingSend earlier on shutdown

[ https://issues.apache.org/jira/browse/KAFKA-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-6051: -- Assignee: Maytee Chinavanichkit > ReplicaFetcherThread should close the ReplicaFetcherBlockingSend earl

[jira] [Commented] (KAFKA-6051) ReplicaFetcherThread should close the ReplicaFetcherBlockingSend earlier on shutdown

[ https://issues.apache.org/jira/browse/KAFKA-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209685#comment-16209685 ] ASF GitHub Bot commented on KAFKA-6051: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-5642) Use async ZookeeperClient in Controller

[ https://issues.apache.org/jira/browse/KAFKA-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209626#comment-16209626 ] ASF GitHub Bot commented on KAFKA-5642: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-5642) Use async ZookeeperClient in Controller

[ https://issues.apache.org/jira/browse/KAFKA-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5642. Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 3765 [https://github.com/apache

[jira] [Commented] (KAFKA-4928) Add integration test for DumpLogSegments

[ https://issues.apache.org/jira/browse/KAFKA-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209503#comment-16209503 ] Pavel commented on KAFKA-4928: -- I'd like to work on that > Add integration test for DumpLogS

[jira] [Commented] (KAFKA-6067) how to process when all isr crashed

[ https://issues.apache.org/jira/browse/KAFKA-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209482#comment-16209482 ] Antony Stubbs commented on KAFKA-6067: -- Are you including the leader? If all the foll

[jira] [Commented] (KAFKA-6062) Reduce topic partition count in kafka version 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209446#comment-16209446 ] Antony Stubbs commented on KAFKA-6062: -- Are you sure this is partition count, and not

[jira] [Commented] (KAFKA-5978) Transient failure in SslTransportLayerTest.testNetworkThreadTimeRecorded

[ https://issues.apache.org/jira/browse/KAFKA-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209382#comment-16209382 ] Manikumar commented on KAFKA-5978: -- [~rsivaram] SslTransportLayerTest.testNetworkThreadT

[jira] [Commented] (KAFKA-5027) Kafka Controller Redesign

[ https://issues.apache.org/jira/browse/KAFKA-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209377#comment-16209377 ] Ted Yu commented on KAFKA-5027: --- If there is dependency among the 'Use ZookeeperClient in' t

[jira] [Created] (KAFKA-6078) Investigate failure of ReassignPartitionsClusterTest.shouldExpandCluster

Dong Lin created KAFKA-6078: --- Summary: Investigate failure of ReassignPartitionsClusterTest.shouldExpandCluster Key: KAFKA-6078 URL: https://issues.apache.org/jira/browse/KAFKA-6078 Project: Kafka

[jira] [Commented] (KAFKA-6063) StreamsException is thrown after the changing `partitions`

[ https://issues.apache.org/jira/browse/KAFKA-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209264#comment-16209264 ] Akihito Nakano commented on KAFKA-6063: --- I had overlooked the error message that Str

[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=16209195#comment-16209195 ] Ben Corlett commented on KAFKA-6042: So far after a week. No issues. > Kafka Request

[jira] [Commented] (KAFKA-6023) ThreadCache#sizeBytes() should check overflow

[ https://issues.apache.org/jira/browse/KAFKA-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208994#comment-16208994 ] ASF GitHub Bot commented on KAFKA-6023: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-6023) ThreadCache#sizeBytes() should check overflow

[ https://issues.apache.org/jira/browse/KAFKA-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6023. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4041 [https://github.com/