[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240928#comment-16240928
]
Jun Rao commented on KAFKA-5473:
[~prasincs], after the discussion in KIP-217, we decided
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241272#comment-16241272
]
Jun Rao commented on KAFKA-5473:
[~prasincs], thanks. I think the existing zk state metric
Jun Rao created KAFKA-6184:
--
Summary: report a metric of the lag between the consumer offset
and the start offset of the log
Key: KAFKA-6184
URL: https://issues.apache.org/jira/browse/KAFKA-6184
Project: Kaf
[
https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244270#comment-16244270
]
Jun Rao commented on KAFKA-6184:
[~huxi_2b], thanks for your the patch. Since this is a pu
[
https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246938#comment-16246938
]
Jun Rao commented on KAFKA-6194:
In 1.0.0, because of KIP-112, the handling of IOException
[
https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247824#comment-16247824
]
Jun Rao commented on KAFKA-6194:
[~corlettb], thanks for the info. You may want to restart
[
https://issues.apache.org/jira/browse/KAFKA-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6175.
Resolution: Fixed
> AbstractIndex should cache index file to avoid unnecessary disk access during
> resize(
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248033#comment-16248033
]
Jun Rao commented on KAFKA-5473:
[~prasincs], thanks. Another thing that I mentioned in th
[
https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248602#comment-16248602
]
Jun Rao commented on KAFKA-6194:
[~corlettb], thanks for the info. It seems that the delet
[
https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249855#comment-16249855
]
Jun Rao commented on KAFKA-6194:
[~corlettb], thanks for the info. As Ismael mentioned, th
[
https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254671#comment-16254671
]
Jun Rao commented on KAFKA-6194:
[~corlettb], if the compaction is very aggressive, it is
[
https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267089#comment-16267089
]
Jun Rao commented on KAFKA-1120:
[~mimaison], yes, the issue is still not fixed in trunk.
[
https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267123#comment-16267123
]
Jun Rao commented on KAFKA-1120:
[~mimaison], thanks for helping out!
> Controller could
[
https://issues.apache.org/jira/browse/KAFKA-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-6065:
--
Assignee: Ismael Juma (was: Prasanna Gautam)
> Add zookeeper metrics to ZookeeperClient as in KIP-188
Jun Rao created KAFKA-6320:
--
Summary: move ZK metrics in KafkaHealthCheck to ZookeeperClient
Key: KAFKA-6320
URL: https://issues.apache.org/jira/browse/KAFKA-6320
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290252#comment-16290252
]
Jun Rao commented on KAFKA-6361:
Was unclean leader election enabled in this case? When br
[
https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291812#comment-16291812
]
Jun Rao commented on KAFKA-6361:
[~hachikuji], thanks for the info. The problem in the des
[
https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293473#comment-16293473
]
Jun Rao commented on KAFKA-3410:
[~wushujames], yes, KAFKA-1211 should help address this.
[
https://issues.apache.org/jira/browse/KAFKA-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300685#comment-16300685
]
Jun Rao commented on KAFKA-6320:
https://github.com/apache/kafka/pull/4351
> move ZK metr
[
https://issues.apache.org/jira/browse/KAFKA-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312337#comment-16312337
]
Jun Rao commented on KAFKA-6116:
With 25K partitions, a replication factor of 2 and 5 brok
[
https://issues.apache.org/jira/browse/KAFKA-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312339#comment-16312339
]
Jun Rao commented on KAFKA-5642:
With 25K partitions, a replication factor of 2 and 5 brok
[
https://issues.apache.org/jira/browse/KAFKA-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339830#comment-16339830
]
Jun Rao commented on KAFKA-6254:
https://github.com/apache/kafka/pull/4418
> Introduce In
[
https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340295#comment-16340295
]
Jun Rao commented on KAFKA-5886:
https://github.com/apache/kafka/pull/3849
> Introduce de
[
https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341863#comment-16341863
]
Jun Rao commented on KAFKA-2729:
The problem that we fixed related to this jira is KAFKA-5
[
https://issues.apache.org/jira/browse/KAFKA-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352667#comment-16352667
]
Jun Rao commented on KAFKA-6469:
[~ambroff], thanks for reporting this. Is the # of childr
[
https://issues.apache.org/jira/browse/KAFKA-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6254.
Resolution: Fixed
Fix Version/s: 1.1.0
The PR is merged.
> Introduce Incremental FetchRequests to In
[
https://issues.apache.org/jira/browse/KAFKA-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352719#comment-16352719
]
Jun Rao commented on KAFKA-6254:
Some perf results from [~afalko].
Without patch @46k pa
[
https://issues.apache.org/jira/browse/KAFKA-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6452.
Resolution: Fixed
Fix Version/s: (was: 1.2.0)
1.1.0
The PR is merged to 1.1 an
[
https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6184.
Resolution: Fixed
Fix Version/s: 1.2.0
The PR is merged to trunk.
> report a metric of the lag betwe
[
https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364973#comment-16364973
]
Jun Rao commented on KAFKA-6549:
We can fix this issue with the updated version in
https:
[
https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366546#comment-16366546
]
Jun Rao commented on KAFKA-4277:
[~nico.meyer], do you know if the conflicting ephemeral n
[
https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387125#comment-16387125
]
Jun Rao commented on KAFKA-3978:
Agreed. For 1) we could add an assertion. For 2), if we d
Jun Rao created KAFKA-6624:
--
Summary: log segment deletion could cause a disk to be marked
offline incorrectly
Key: KAFKA-6624
URL: https://issues.apache.org/jira/browse/KAFKA-6624
Project: Kafka
I
[
https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390572#comment-16390572
]
Jun Rao commented on KAFKA-6624:
One way to fix this is to add a flag for a log segment to
[
https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390727#comment-16390727
]
Jun Rao commented on KAFKA-6624:
[~lindong], do you think this is an issue? Thanks.
> log
[
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
Jun Rao created KAFKA-6760:
--
Summary: responses not logged properly in controller
Key: KAFKA-6760
URL: https://issues.apache.org/jira/browse/KAFKA-6760
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-3827.
Resolution: Won't Fix
The currently implementation is easier to understand than what I proposed.
Closing th
[
https://issues.apache.org/jira/browse/KAFKA-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-5706.
Resolution: Cannot Reproduce
[~manasvigupta], this doesn't seem to be an issue any more now that we have
co
[
https://issues.apache.org/jira/browse/KAFKA-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-6752.
Resolution: Fixed
Fix Version/s: 1.1.1
2.0.0
Merged to trunk and 1.1.
> Unclean l
[
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
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-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
[
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
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-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-6857:
--
Summary: LeaderEpochFileCache.endOffsetFor() should check for
UNDEFINED_EPOCH explicitly
Key: KAFKA-6857
URL: https://issues.apache.org/jira/browse/KAFKA-6857
Project: Kafka
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
[
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-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-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
[
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:
---
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: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 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-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-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-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-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-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-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-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-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-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-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-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
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-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
[
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-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-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: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-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-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
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-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
[
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-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-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-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-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-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15046.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk.
> Produce performance issue under
Jun Rao created KAFKA-15950:
---
Summary: CommunicationEvent should be scheduled with
EarliestDeadlineFunction
Key: KAFKA-15950
URL: https://issues.apache.org/jira/browse/KAFKA-15950
Project: Kafka
I
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791367#comment-17791367
]
Jun Rao commented on KAFKA-15950:
-
cc [~soarez]
> CommunicationEvent should be schedul
[
https://issues.apache.org/jira/browse/KAFKA-15965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15965.
-
Fix Version/s: 3.7.0
Assignee: Colin McCabe
Resolution: Fixed
This is fixed by https://g
[
https://issues.apache.org/jira/browse/KAFKA-15831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15831.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk.
> List Client Metrics Configurati
[
https://issues.apache.org/jira/browse/KAFKA-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15871.
-
Resolution: Fixed
merged the PR to trunk
> Implement kafka-client-metrics.sh tool
> ---
[
https://issues.apache.org/jira/browse/KAFKA-15684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15684.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk.
> Add support to describe all sub
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-15950:
Summary: Serialize broker heartbeat requests (was: CommunicationEvent
should be scheduled with EarliestDe
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-15950:
Description:
{{KafkaEventQueue}} does de-duping and only allows one outstanding
{{CommunicationEvent}} in
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-15950:
Description:
{{KafkaEventQueue}} does de-duping and only allows one outstanding
{{CommunicationEvent}} in
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-15950:
Description:
This is a follow up issue from the discussion in
https://github.com/apache/kafka/pull/14836#
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-15950:
Description:
This is a followup issue from the discussion in
[https://github.com/apache/kafka/pull/14836#
[
https://issues.apache.org/jira/browse/KAFKA-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842783#comment-17842783
]
Jun Rao commented on KAFKA-16541:
-
[~ocadaruma] : Will you be able to work on this soon?
[
https://issues.apache.org/jira/browse/KAFKA-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-16541.
-
Fix Version/s: 4.0.0
Resolution: Fixed
Merged the PR to trunk.
> Potential leader epoch checkpoi
Jun Rao created KAFKA-17076:
---
Summary: logEndOffset could be lost due to log cleaning
Key: KAFKA-17076
URL: https://issues.apache.org/jira/browse/KAFKA-17076
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862868#comment-17862868
]
Jun Rao commented on KAFKA-17076:
-
One potential solution is to adjust the log cleaning
[
https://issues.apache.org/jira/browse/KAFKA-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866122#comment-17866122
]
Jun Rao commented on KAFKA-17076:
-
[~ocadaruma], thanks for the comment.
{noformat}
At t
[
https://issues.apache.org/jira/browse/KAFKA-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866122#comment-17866122
]
Jun Rao edited comment on KAFKA-17076 at 7/15/24 4:49 PM:
--
[~oc
401 - 500 of 522 matches
Mail list logo
