[jira] [Commented] (KAFKA-1368) Upgrade log4j

[ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394956#comment-16394956 ] Gérald Quintana commented on KAFKA-1368: How is this related to https://issues.apa

[jira] [Commented] (KAFKA-6317) Maven artifact for kafka should not depend on log4j

[ https://issues.apache.org/jira/browse/KAFKA-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394958#comment-16394958 ] Gérald Quintana commented on KAFKA-6317: Does that mean that we can replace Log4J1

[jira] [Commented] (KAFKA-4493) Connections to Kafka brokers should be validated

[ https://issues.apache.org/jira/browse/KAFKA-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395002#comment-16395002 ] ASF GitHub Bot commented on KAFKA-4493: --- taku-k closed pull request #2408: KAFKA-449

[jira] [Commented] (KAFKA-6474) Rewrite test to use new public TopologyTestDriver

[ https://issues.apache.org/jira/browse/KAFKA-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395070#comment-16395070 ] Filipe Agapito commented on KAFKA-6474: --- Hi John, So far I've done most of the refac

[jira] [Commented] (KAFKA-6556) allow to attach callbacks in kafka streams, to be triggered when a window is expired

[ https://issues.apache.org/jira/browse/KAFKA-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395095#comment-16395095 ] Abhishek Agarwal commented on KAFKA-6556: - I am working on something similar (curr

[jira] [Resolved] (KAFKA-6337) Error for partition [__consumer_offsets,15] to broker

[ https://issues.apache.org/jira/browse/KAFKA-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6337. -- Resolution: Cannot Reproduce Please reopen if you think the issue still exists > Error for partition [_

[jira] [Commented] (KAFKA-6195) DNS alias support for secured connections

[ https://issues.apache.org/jira/browse/KAFKA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395521#comment-16395521 ] Jonathan Skrzypek commented on KAFKA-6195: -- updated the KIP, thoughts ? > DNS al

[jira] [Resolved] (KAFKA-5467) setting offset retention minutes to a lower value is not reflecting

[ https://issues.apache.org/jira/browse/KAFKA-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5467. -- Resolution: Cannot Reproduce Closing inactive issue. Please reopen if you think the issue exists. > set

[jira] [Resolved] (KAFKA-6022) mirror maker stores offset in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6022. -- Resolution: Not A Problem Please reopen if you think the issue still exists > mirror maker stores offse

[jira] [Resolved] (KAFKA-5504) Kafka controller is not getting elected

[ https://issues.apache.org/jira/browse/KAFKA-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5504. -- Resolution: Not A Problem Closing as per above comments. > Kafka controller is not getting elected > --

[jira] [Resolved] (KAFKA-4984) Unable to produce or consume when enabling authentication SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4984. -- Resolution: Cannot Reproduce {color:#00}Closing inactive issue. Please reopen if you think the issue

[jira] [Assigned] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-6624: --- Assignee: Dong Lin > log segment deletion could cause a disk to be marked offline incorrectly > -

[jira] [Created] (KAFKA-6636) ReplicaFetcherThread should not die if hw < 0

Dong Lin created KAFKA-6636: --- Summary: ReplicaFetcherThread should not die if hw < 0 Key: KAFKA-6636 URL: https://issues.apache.org/jira/browse/KAFKA-6636 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-6637) if set topic config segment.ms=0 Kafka broker won't be able to start

Chong Wang created KAFKA-6637: - Summary: if set topic config segment.ms=0 Kafka broker won't be able to start Key: KAFKA-6637 URL: https://issues.apache.org/jira/browse/KAFKA-6637 Project: Kafka

[jira] [Updated] (KAFKA-6637) if set topic config segment.ms=0 Kafka broker won't be able to start

[ https://issues.apache.org/jira/browse/KAFKA-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chong Wang updated KAFKA-6637: -- Affects Version/s: 1.0.0 > if set topic config segment.ms=0 Kafka broker won't be able to start > --

[jira] [Commented] (KAFKA-6560) Use single-point queries than range queries for windowed aggregation operators

[ https://issues.apache.org/jira/browse/KAFKA-6560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395807#comment-16395807 ] ASF GitHub Bot commented on KAFKA-6560: --- guozhangwang closed pull request #4685: KAF

[jira] [Updated] (KAFKA-6636) ReplicaFetcherThread should not die if hw < 0

[ https://issues.apache.org/jira/browse/KAFKA-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6636: Description: ReplicaFetcherThread can die in the following scenario:   1) Partition P1 has replica set siz

[jira] [Created] (KAFKA-6638) Controller should remove replica from ISR if the replica is removed from the replica set

Dong Lin created KAFKA-6638: --- Summary: Controller should remove replica from ISR if the replica is removed from the replica set Key: KAFKA-6638 URL: https://issues.apache.org/jira/browse/KAFKA-6638 Project:

[jira] [Updated] (KAFKA-6535) Set default retention ms for Streams repartition topics to Long.MAX_VALUE

[ https://issues.apache.org/jira/browse/KAFKA-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6535: - Summary: Set default retention ms for Streams repartition topics to Long.MAX_VALUE (was: Set defa

[jira] [Commented] (KAFKA-6535) Set default retention ms for Streams repartition topics to Long.MAX_VALUE

[ https://issues.apache.org/jira/browse/KAFKA-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395884#comment-16395884 ] Guozhang Wang commented on KAFKA-6535: -- Makes sense, I've changed the title according

[jira] [Updated] (KAFKA-6535) Set default retention ms for Streams repartition topics to Long.MAX_VALUE

[ https://issues.apache.org/jira/browse/KAFKA-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6535: - Description: After KIP-220 / KIP-204, repartition topics in Streams are transient, so it is bette

[jira] [Created] (KAFKA-6639) Follower may have sparse index if catching up

Jason Gustafson created KAFKA-6639: -- Summary: Follower may have sparse index if catching up Key: KAFKA-6639 URL: https://issues.apache.org/jira/browse/KAFKA-6639 Project: Kafka Issue Type: B

[jira] [Commented] (KAFKA-5540) Deprecate and remove internal converter configs

[ https://issues.apache.org/jira/browse/KAFKA-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396134#comment-16396134 ] ASF GitHub Bot commented on KAFKA-5540: --- C0urante opened a new pull request #4693: K

[jira] [Resolved] (KAFKA-3368) Add the Message/Record set protocol to the protocol docs

[ https://issues.apache.org/jira/browse/KAFKA-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3368. Resolution: Fixed Fix Version/s: 1.2.0 > Add the Message/Record set protocol to the p

[jira] [Assigned] (KAFKA-4831) Extract WindowedSerde to public APIs

[ https://issues.apache.org/jira/browse/KAFKA-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4831: Resolution: Fixed Assignee: Guozhang Wang (was: Vitaly Pushkar) Fix Version

[jira] [Created] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

Dong Lin created KAFKA-6640: --- Summary: Improve efficiency of KafkaAdminClient.describeTopics() Key: KAFKA-6640 URL: https://issues.apache.org/jira/browse/KAFKA-6640 Project: Kafka Issue Type: Impro

[jira] [Updated] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

[ https://issues.apache.org/jira/browse/KAFKA-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6640: Description: Currently in KafkaAdminClient.describeTopics(), for each topic in the request, an complete map

[jira] [Updated] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

[ https://issues.apache.org/jira/browse/KAFKA-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6640: Description: Currently in KafkaAdminClient.describeTopics(), for each topic in the request, an complete map

[jira] [Updated] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

[ https://issues.apache.org/jira/browse/KAFKA-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6640: Description: Currently in KafkaAdminClient.describeTopics(), for each topic in the request, an complete map

[jira] [Updated] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

[ https://issues.apache.org/jira/browse/KAFKA-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6640: Description: Currently in KafkaAdminClient.describeTopics(), for each topic in the request, an complete map

[jira] [Commented] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

[ https://issues.apache.org/jira/browse/KAFKA-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396241#comment-16396241 ] ASF GitHub Bot commented on KAFKA-6640: --- lindong28 opened a new pull request #4694:

[jira] [Created] (KAFKA-6641) Consider auto repartitioning for Stream.transform() API

Guozhang Wang created KAFKA-6641: Summary: Consider auto repartitioning for Stream.transform() API Key: KAFKA-6641 URL: https://issues.apache.org/jira/browse/KAFKA-6641 Project: Kafka Issue T

[jira] [Updated] (KAFKA-6641) Consider auto repartitioning for Stream.transform() API

[ https://issues.apache.org/jira/browse/KAFKA-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6641: - Labels: api (was: ) > Consider auto repartitioning for Stream.transform() API > -

[jira] [Commented] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396305#comment-16396305 ] ASF GitHub Bot commented on KAFKA-3978: --- lindong28 opened a new pull request #4695:

[jira] [Commented] (KAFKA-6631) Kafka Streams - Rebalancing exception in Kafka 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396307#comment-16396307 ] Guozhang Wang commented on KAFKA-6631: -- If you are certain that I do not see the erro

[jira] [Updated] (KAFKA-6638) Leader should remove unassigned replica from ISR

[ https://issues.apache.org/jira/browse/KAFKA-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6638: Summary: Leader should remove unassigned replica from ISR (was: Controller should remove replica from ISR i

[jira] [Commented] (KAFKA-6638) Leader should remove unassigned replica from ISR

[ https://issues.apache.org/jira/browse/KAFKA-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396325#comment-16396325 ] ASF GitHub Bot commented on KAFKA-6638: --- lindong28 opened a new pull request #4696:

[jira] [Updated] (KAFKA-6638) Leader should remove unassigned replica from ISR

[ https://issues.apache.org/jira/browse/KAFKA-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6638: Description: During partition reassignment, controller may remove a replica from the replica set while still

[jira] [Commented] (KAFKA-6555) Making state store queryable during restoration

[ https://issues.apache.org/jira/browse/KAFKA-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396531#comment-16396531 ] Ashish Surana commented on KAFKA-6555: -- +1. Let me capture all the approaches in KIP,

[jira] [Created] (KAFKA-6642) Rack aware replica assignment in kafka streams

Ashish Surana created KAFKA-6642: Summary: Rack aware replica assignment in kafka streams Key: KAFKA-6642 URL: https://issues.apache.org/jira/browse/KAFKA-6642 Project: Kafka Issue Type: New

[jira] [Commented] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396554#comment-16396554 ] ASF GitHub Bot commented on KAFKA-6624: --- junrao closed pull request #4663: KAFKA-662

[jira] [Resolved] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6624. Resolution: Fixed Fix Version/s: 1.1.0 > log segment deletion could cause a disk to be marked offline

[jira] [Created] (KAFKA-6643) Warm up new replicas from scratch when changelog topic has retention time

Navinder Brar created KAFKA-6643: Summary: Warm up new replicas from scratch when changelog topic has retention time Key: KAFKA-6643 URL: https://issues.apache.org/jira/browse/KAFKA-6643 Project: Kafk

[jira] [Updated] (KAFKA-6643) Warm up new replicas from scratch when changelog topic has retention time

[ https://issues.apache.org/jira/browse/KAFKA-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navinder Brar updated KAFKA-6643: - Description: In the current scenario, Kafka Streams has changelog Kafka topics(internal topics ha

[jira] [Updated] (KAFKA-6643) Warm up new replicas from scratch when changelog topic has LIMITED retention time

[ https://issues.apache.org/jira/browse/KAFKA-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navinder Brar updated KAFKA-6643: - Summary: Warm up new replicas from scratch when changelog topic has LIMITED retention time (was:

[jira] [Updated] (KAFKA-6643) Warm up new replicas from scratch when changelog topic has LIMITED retention time

[ https://issues.apache.org/jira/browse/KAFKA-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navinder Brar updated KAFKA-6643: - Description: In the current scenario, Kafka Streams has changelog Kafka topics(internal topics ha

[jira] [Updated] (KAFKA-6643) Warm up new replicas from scratch when changelog topic has LIMITED retention time

[ https://issues.apache.org/jira/browse/KAFKA-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navinder Brar updated KAFKA-6643: - Description: In the current scenario, Kafka Streams has changelog Kafka topics(internal topics ha

[jira] [Resolved] (KAFKA-6024) Consider moving validation in KafkaConsumer ahead of call to acquireAndEnsureOpen()

[ https://issues.apache.org/jira/browse/KAFKA-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6024. Resolution: Fixed Fix Version/s: 1.2.0 > Consider moving validation in KafkaConsumer

[jira] [Commented] (KAFKA-6024) Consider moving validation in KafkaConsumer ahead of call to acquireAndEnsureOpen()

[ https://issues.apache.org/jira/browse/KAFKA-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396592#comment-16396592 ] ASF GitHub Bot commented on KAFKA-6024: --- hachikuji closed pull request #4617: KAFKA-

[jira] [Commented] (KAFKA-6555) Making state store queryable during restoration

[ https://issues.apache.org/jira/browse/KAFKA-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396593#comment-16396593 ] Matthias J. Sax commented on KAFKA-6555: Thanks [~asurana]! Looking forward to you

[jira] [Updated] (KAFKA-6617) Improve controller performance by batching reassignment znode write operation

[ https://issues.apache.org/jira/browse/KAFKA-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6617: Summary: Improve controller performance by batching reassignment znode write operation (was: KAFKA-6617; Im

[jira] [Updated] (KAFKA-6617) KAFKA-6617; Improve controller performance by batching reassignment znode write operation

[ https://issues.apache.org/jira/browse/KAFKA-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6617: Summary: KAFKA-6617; Improve controller performance by batching reassignment znode write operation (was: Im