Jun Rao created KAFKA-7987:
--
Summary: a broker's ZK session may die on transient auth failure
Key: KAFKA-7987
URL: https://issues.apache.org/jira/browse/KAFKA-7987
Project: Kafka
Issue Type: Improve
[
https://issues.apache.org/jira/browse/KAFKA-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775560#comment-16775560
]
Jun Rao commented on KAFKA-7986:
This can potentially be done by passing in a clientID st
Jun Rao created KAFKA-7986:
--
Summary: distinguish the logging from different ZooKeeperClient
instances
Key: KAFKA-7986
URL: https://issues.apache.org/jira/browse/KAFKA-7986
Project: Kafka
Issue Typ
Jun Rao created KAFKA-7983:
--
Summary: supporting replication.throttled.replicas in dynamic
broker configuration
Key: KAFKA-7983
URL: https://issues.apache.org/jira/browse/KAFKA-7983
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7864.
Resolution: Fixed
Fix Version/s: 2.3.0
Merged the PR to trunk.
> AdminZkClient.validateTopicCreate(
[
https://issues.apache.org/jira/browse/KAFKA-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7283.
Resolution: Fixed
Fix Version/s: 2.3.0
Merged the PR to trunk.
> mmap indexes lazily and skip sanit
[
https://issues.apache.org/jira/browse/KAFKA-7888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758638#comment-16758638
]
Jun Rao commented on KAFKA-7888:
[~kemalerden], from the log, the "Cached zkVersion" log
[
https://issues.apache.org/jira/browse/KAFKA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7837.
Resolution: Fixed
Fix Version/s: 2.2.0
Merged the PR to trunk.
> maybeShrinkIsr may not reflect Off
[
https://issues.apache.org/jira/browse/KAFKA-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7838.
Resolution: Fixed
Fix Version/s: 2.2.0
Merged the PR to trunk.
> improve logging in Partition.maybe
[
https://issues.apache.org/jira/browse/KAFKA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751766#comment-16751766
]
Jun Rao commented on KAFKA-7837:
[~dhruvilshah], the following is the description of the
Jun Rao created KAFKA-7864:
--
Summary: AdminZkClient.validateTopicCreate() should validate that
partitions are 0-based
Key: KAFKA-7864
URL: https://issues.apache.org/jira/browse/KAFKA-7864
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746520#comment-16746520
]
Jun Rao commented on KAFKA-7837:
@lindong, yes, the approach that you described sounds go
Jun Rao created KAFKA-7838:
--
Summary: improve logging in Partition.maybeShrinkIsr()
Key: KAFKA-7838
URL: https://issues.apache.org/jira/browse/KAFKA-7838
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745680#comment-16745680
]
Jun Rao commented on KAFKA-7837:
One way to improve this is that in maybeShrinkIsr(), for
Jun Rao created KAFKA-7837:
--
Summary: maybeShrinkIsr may not reflect OfflinePartitions
immediately
Key: KAFKA-7837
URL: https://issues.apache.org/jira/browse/KAFKA-7837
Project: Kafka
Issue Type: I
[
https://issues.apache.org/jira/browse/KAFKA-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745672#comment-16745672
]
Jun Rao commented on KAFKA-7836:
[~lindong], it seems that we could call zkClient.propaga
Jun Rao created KAFKA-7836:
--
Summary: The propagation of log dir failure can be delayed due to
slowness in closing the file handles
Key: KAFKA-7836
URL: https://issues.apache.org/jira/browse/KAFKA-7836
Proje
[
https://issues.apache.org/jira/browse/KAFKA-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7829.
Resolution: Fixed
Fix Version/s: 2.2.0
Merged to trunk.
> Javadoc should show that AdminClient.alte
Jun Rao created KAFKA-7829:
--
Summary: Inaccurate description for --reassignment-json-file
option in ReassignPartitionsCommand
Key: KAFKA-7829
URL: https://issues.apache.org/jira/browse/KAFKA-7829
Project: Ka
[
https://issues.apache.org/jira/browse/KAFKA-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744272#comment-16744272
]
Jun Rao commented on KAFKA-7829:
[~lindong], could you verify if this is inaccurate?
> I
[
https://issues.apache.org/jira/browse/KAFKA-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736415#comment-16736415
]
Jun Rao commented on KAFKA-7786:
Great find, Anna. About the fix. I am not sure that we n
[
https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722217#comment-16722217
]
Jun Rao commented on KAFKA-7297:
[~lindong], good points. The current implementation is n
[
https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721960#comment-16721960
]
Jun Rao commented on KAFKA-7297:
[~lindong], Ismael pointed out that ConcurrentSkipListMa
[
https://issues.apache.org/jira/browse/KAFKA-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721607#comment-16721607
]
Jun Rao commented on KAFKA-7681:
[~mgharat], Meter is calculated by (accumulated values /
[
https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720819#comment-16720819
]
Jun Rao commented on KAFKA-2729:
[~murri71], my earlier comment was referring to that we
[
https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720710#comment-16720710
]
Jun Rao commented on KAFKA-7297:
To follow up on that, another related issue is that curr
[
https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719228#comment-16719228
]
Jun Rao commented on KAFKA-5692:
[~tombentley], that's good to know. Thanks for your help
[
https://issues.apache.org/jira/browse/KAFKA-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718002#comment-16718002
]
Jun Rao commented on KAFKA-7713:
io-wait-ratio is calculated as the ratio of accumulated
[
https://issues.apache.org/jira/browse/KAFKA-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716273#comment-16716273
]
Jun Rao commented on KAFKA-7680:
[~NIzhikov], thanks for your interest. Feel free to assi
[
https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713395#comment-16713395
]
Jun Rao commented on KAFKA-5692:
[~tombentley], thanks for contributing the PR. Would be
[
https://issues.apache.org/jira/browse/KAFKA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7704.
Resolution: Fixed
Fix Version/s: 2.1.1
2.2.0
Merged to trunk and 2.1.
> kafka.se
[
https://issues.apache.org/jira/browse/KAFKA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709589#comment-16709589
]
Jun Rao commented on KAFKA-7704:
[~yuyang08], could you try the PR and see if it fixes th
[
https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709539#comment-16709539
]
Jun Rao commented on KAFKA-2729:
We fixed another issue that can fail the re-creation of
[
https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1120.
Resolution: Fixed
Assignee: Zhanxiang (Patrick) Huang (was: Mickael Maison)
This is fixed by KAFKA-7
[
https://issues.apache.org/jira/browse/KAFKA-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7235.
Resolution: Fixed
Fix Version/s: 2.2.0
merged to trunk.
> Use brokerZkNodeVersion to prevent broker
[
https://issues.apache.org/jira/browse/KAFKA-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7449.
Resolution: Fixed
Assignee: Mathieu Chataigner
Fix Version/s: 2.2.0
Merged to trunk.
> Kaf
[
https://issues.apache.org/jira/browse/KAFKA-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702176#comment-16702176
]
Jun Rao commented on KAFKA-7681:
Hi, [~mgharat],
The Broker Topic metrics only collect t
Jun Rao created KAFKA-7682:
--
Summary: turning on request logging for a subset of request types
Key: KAFKA-7682
URL: https://issues.apache.org/jira/browse/KAFKA-7682
Project: Kafka
Issue Type: Improv
Jun Rao created KAFKA-7681:
--
Summary: new metric for request thread utilization by request type
Key: KAFKA-7681
URL: https://issues.apache.org/jira/browse/KAFKA-7681
Project: Kafka
Issue Type: Impro
[
https://issues.apache.org/jira/browse/KAFKA-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701084#comment-16701084
]
Jun Rao commented on KAFKA-7680:
One way to fix this is the following. We already include
Jun Rao created KAFKA-7680:
--
Summary: fetching a refilled chunk of log can cause log divergence
Key: KAFKA-7680
URL: https://issues.apache.org/jira/browse/KAFKA-7680
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692047#comment-16692047
]
Jun Rao commented on KAFKA-4277:
[~birger] : Hmm, according to
[http://mail-archives.apa
[
https://issues.apache.org/jira/browse/KAFKA-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7557.
Resolution: Fixed
Fix Version/s: 2.2.0
merged to trunk
> optimize LogManager.truncateFullyAndStartA
[
https://issues.apache.org/jira/browse/KAFKA-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7412.
Resolution: Fixed
Fix Version/s: 2.2.0
Clarified the javadoc in producer callback. Metadata is not n
[
https://issues.apache.org/jira/browse/KAFKA-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7537.
Resolution: Fixed
Fix Version/s: 2.2.0
Merged the PR to trunk.
> Only include live brokers in the U
[
https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667977#comment-16667977
]
Jun Rao commented on KAFKA-7481:
I agree that introducing a new config probably needs mor
[
https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667914#comment-16667914
]
Jun Rao commented on KAFKA-7165:
[~pachilo], your PR actually looks reasonable for addres
[
https://issues.apache.org/jira/browse/KAFKA-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665737#comment-16665737
]
Jun Rao commented on KAFKA-7557:
To improve this, instead of calling
Log.deleteSnapshots
Jun Rao created KAFKA-7557:
--
Summary: optimize LogManager.truncateFullyAndStartAt()
Key: KAFKA-7557
URL: https://issues.apache.org/jira/browse/KAFKA-7557
Project: Kafka
Issue Type: Bug
Affects V
[
https://issues.apache.org/jira/browse/KAFKA-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662538#comment-16662538
]
Jun Rao commented on KAFKA-7538:
[~rsivaram], thanks for the analysis. I agree that appro
[
https://issues.apache.org/jira/browse/KAFKA-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-7299:
---
Fix Version/s: 2.0.1
1.1.2
Kevin, since this is a small patch, I merged it to both 1.1 and
[
https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650798#comment-16650798
]
Jun Rao commented on KAFKA-7504:
The case that Allen described is when a follower is fetc
[
https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649546#comment-16649546
]
Jun Rao commented on KAFKA-7504:
[~kawamuray], thanks for the jira. Great find. Simple, b
[
https://issues.apache.org/jira/browse/KAFKA-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7482.
Resolution: Fixed
Fix Version/s: 2.1.0
merged to 2.1 and trunk
> LeaderAndIsrRequest should be sent
[
https://issues.apache.org/jira/browse/KAFKA-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-3097.
Resolution: Fixed
Assignee: Manikumar (was: Ashish Singh)
Fix Version/s: 2.1.0
Merged to 2
[
https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7366.
Resolution: Fixed
Fix Version/s: 2.1.0
Merged to 2.1 and trunk.
> topic level segment.bytes and seg
[
https://issues.apache.org/jira/browse/KAFKA-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7215.
Resolution: Fixed
Fix Version/s: 2.1.0
Merged to 2.1 and trunk.
> Improve LogCleaner behavior on er
Jun Rao created KAFKA-7482:
--
Summary: LeaderAndIsrRequest should be sent to the shutting down
broker
Key: KAFKA-7482
URL: https://issues.apache.org/jira/browse/KAFKA-7482
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7216.
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
1.1.2
[
https://issues.apache.org/jira/browse/KAFKA-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7400.
Resolution: Fixed
Fix Version/s: 2.1.0
Merged the PR to trunk.
> Compacted topic segments that prec
[
https://issues.apache.org/jira/browse/KAFKA-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615492#comment-16615492
]
Jun Rao commented on KAFKA-7408:
It does seem that truncating to LSO handles unclean lead
[
https://issues.apache.org/jira/browse/KAFKA-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7117.
Resolution: Fixed
Fix Version/s: 2.1.0
Merged the PR to trunk.
> Allow AclCommand to use AdminClien
[
https://issues.apache.org/jira/browse/KAFKA-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7287.
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
1.1.2
Also merged
[
https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599003#comment-16599003
]
Jun Rao commented on KAFKA-7366:
[~ijuma], it might be debatable. However, if all other t
Jun Rao created KAFKA-7366:
--
Summary: topic level segment.bytes and segment.ms not taking
effect immediately
Key: KAFKA-7366
URL: https://issues.apache.org/jira/browse/KAFKA-7366
Project: Kafka
Iss
[
https://issues.apache.org/jira/browse/KAFKA-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595702#comment-16595702
]
Jun Rao commented on KAFKA-7287:
[~omkreddy], thanks for the patch. I merged the PR to tr
[
https://issues.apache.org/jira/browse/KAFKA-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6343.
Resolution: Fixed
Assignee: Alex Dunayevsky
Fix Version/s: 2.1.0
Merged the PR to trunk.
>
[
https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588220#comment-16588220
]
Jun Rao commented on KAFKA-6753:
[~luwang], that sounds good too. To make tracking easier
[
https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588026#comment-16588026
]
Jun Rao commented on KAFKA-6753:
[~luwang], we could consider removing this metric, but i
[
https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6753.
Resolution: Fixed
Fix Version/s: 2.1.0
Merged the PR to trunk.
> Speed up event processing on the c
[
https://issues.apache.org/jira/browse/KAFKA-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6835.
Resolution: Fixed
Merged the PR to trunk.
> Enable topic unclean leader election to be enabled without con
[
https://issues.apache.org/jira/browse/KAFKA-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7299.
Resolution: Fixed
Fix Version/s: 2.1.0
Merged the PR to trunk.
> batch LeaderAndIsr requests during
Jun Rao created KAFKA-7299:
--
Summary: batch LeaderAndIsr requests during auto preferred leader
election
Key: KAFKA-7299
URL: https://issues.apache.org/jira/browse/KAFKA-7299
Project: Kafka
Issue Ty
[
https://issues.apache.org/jira/browse/KAFKA-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551864#comment-16551864
]
Jun Rao commented on KAFKA-7152:
Thanks for reporting the issue. A few things.
# Not sur
[
https://issues.apache.org/jira/browse/KAFKA-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7064.
Resolution: Fixed
Merged [https://github.com/apache/kafka/pull/5245] to trunk and 2.0 branch.
> "Unexpecte
[
https://issues.apache.org/jira/browse/KAFKA-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7010.
Resolution: Fixed
merged the PR to trunk and 2.0 branch.
> Rename ResourceNameType.ANY to MATCH
>
[
https://issues.apache.org/jira/browse/KAFKA-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-7007:
---
Description:
Relating to one of the outstanding work items in PR
[#5117|[https://github.com/apache/kafka/pul
[
https://issues.apache.org/jira/browse/KAFKA-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7007.
Resolution: Fixed
merged the PR to trunk and 2.0 branch.
> Use JSON for /kafka-acl-extended-changes path
>
[
https://issues.apache.org/jira/browse/KAFKA-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-7007:
---
Summary: Use JSON for /kafka-acl-extended-changes path (was: All ACL
changes should use single /kafka-acl-ch
[
https://issues.apache.org/jira/browse/KAFKA-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7005.
Resolution: Fixed
merged the PR to trunk and 2.0 branch.
> Remove duplicate Java Resource class.
> ---
[
https://issues.apache.org/jira/browse/KAFKA-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7006.
Resolution: Fixed
merged the PR to trunk and 2.0 branch.
> Remove duplicate Scala ResourceNameType class
>
[
https://issues.apache.org/jira/browse/KAFKA-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7011.
Resolution: Fixed
Merged the PR to trunk and 2.0 branch.
> Investigate if its possible to drop the Resourc
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495306#comment-16495306
]
Jun Rao commented on KAFKA-3042:
Interesting. Do you have the controller and the state-ch
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493976#comment-16493976
]
Jun Rao commented on KAFKA-3042:
We fixed KAFKA-2729 in 1.1.0 that could lead to Cached z
[
https://issues.apache.org/jira/browse/KAFKA-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491723#comment-16491723
]
Jun Rao commented on KAFKA-6952:
Hmm, could you run bin/kafka-run-class.sh kafka.tools.Dum
[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6937.
Resolution: Fixed
Fix Version/s: 1.1.1
1.0.2
2.0.0
Merged the P
[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491376#comment-16491376
]
Jun Rao commented on KAFKA-6937:
[~klafferty], thanks for testing this out. Yes, the reaso
[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-6937:
---
Component/s: core
> In-sync replica delayed during fetch if replica throttle is exceeded
> ---
[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-6937:
---
Affects Version/s: 0.11.0.1
1.1.0
1.0.1
> In-sync replica delaye
[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-6937:
---
Description:
When replication throttling is enabled, in-sync replica's traffic should never
be throttled. How
Jun Rao created KAFKA-6937:
--
Summary: In-sync replica delayed during fetch if replica throttle
is exceeded
Key: KAFKA-6937
URL: https://issues.apache.org/jira/browse/KAFKA-6937
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6361.
Resolution: Fixed
Fix Version/s: 2.0.0
Merged the PR to trunk.
> Fast leader fail over can lead to l
Jun Rao created KAFKA-6858:
--
Summary: Log.truncateTo() may truncate to an earlier offset than
requested
Key: KAFKA-6858
URL: https://issues.apache.org/jira/browse/KAFKA-6858
Project: Kafka
Issue Ty
Jun Rao created KAFKA-6857:
--
Summary: LeaderEpochFileCache.endOffsetFor() should check for
UNDEFINED_EPOCH explicitly
Key: KAFKA-6857
URL: https://issues.apache.org/jira/browse/KAFKA-6857
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457130#comment-16457130
]
Jun Rao commented on KAFKA-6834:
To fix this, we need to handle the cleaner buffer to grow
Jun Rao created KAFKA-6834:
--
Summary: log cleaner should handle the case when the size of a
message set is larger than the max message size
Key: KAFKA-6834
URL: https://issues.apache.org/jira/browse/KAFKA-6834
[
https://issues.apache.org/jira/browse/KAFKA-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6650.
Resolution: Fixed
Fix Version/s: 2.0.0
merged the PR to trunk.
> The controller should be able to ha
[
https://issues.apache.org/jira/browse/KAFKA-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434646#comment-16434646
]
Jun Rao commented on KAFKA-6780:
The fix is probably to further bound firstUncleanableDirt
Jun Rao created KAFKA-6780:
--
Summary: log cleaner shouldn't clean messages beyond high watermark
Key: KAFKA-6780
URL: https://issues.apache.org/jira/browse/KAFKA-6780
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6447.
Resolution: Fixed
Fix Version/s: 2.0.0
Merged the PR to trunk.
> Add Delegation Token Operations to
301 - 400 of 527 matches
Mail list logo