[
https://issues.apache.org/jira/browse/KAFKA-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842783#comment-17842783
]
Jun Rao commented on KAFKA-16541:
-
[~ocadaruma] : Will you be able to work on this soon? The 3.8.0 code
[
https://issues.apache.org/jira/browse/KAFKA-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836717#comment-17836717
]
Jun Rao edited comment on KAFKA-16541 at 4/12/24 5:43 PM:
--
Thanks for filing
[
https://issues.apache.org/jira/browse/KAFKA-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836717#comment-17836717
]
Jun Rao commented on KAFKA-16541:
-
Thanks for filing the jira, [~ocadaruma] ! Since this is a
[
https://issues.apache.org/jira/browse/KAFKA-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-16541:
Affects Version/s: 3.7.0
> Potential leader epoch checkpoint file corruption on OS crash
>
[
https://issues.apache.org/jira/browse/KAFKA-16485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-16485.
-
Fix Version/s: 3.8.0
Resolution: Fixed
Merged the PR to trunk.
> Fix broker metrics to follow
[
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831959#comment-17831959
]
Jun Rao commented on KAFKA-16310:
-
Since the follower only maintains offsetForMaxTimestamp at the batch
[
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831834#comment-17831834
]
Jun Rao edited comment on KAFKA-16310 at 3/28/24 3:04 PM:
--
[~chia7712] :
[
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831834#comment-17831834
]
Jun Rao commented on KAFKA-16310:
-
[~chia7712] :
{quote}Did you mean that we should change the schema to
[
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831553#comment-17831553
]
Jun Rao commented on KAFKA-16310:
-
[~johnnyhsu] , [~showuon] and [~chia7712] : Sorry, but I just
[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15950.
-
Fix Version/s: 3.8.0
Resolution: Fixed
merged the PR to trunk.
> Serialize broker heartbeat
[
https://issues.apache.org/jira/browse/KAFKA-16385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828506#comment-17828506
]
Jun Rao commented on KAFKA-16385:
-
[~showuon] : Yes, the retention by time is supposed to cover the
[
https://issues.apache.org/jira/browse/KAFKA-16283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819322#comment-17819322
]
Jun Rao commented on KAFKA-16283:
-
[~showuon] : Is this the same as
[
https://issues.apache.org/jira/browse/KAFKA-16186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-16186.
-
Fix Version/s: 3.8.0
Resolution: Fixed
merged the PR to trunk
> Implement broker metrics for
[
https://issues.apache.org/jira/browse/KAFKA-15813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15813.
-
Fix Version/s: 3.8.0
Resolution: Fixed
Merged to the PR to trunk.
> Improve implementation of
[
https://issues.apache.org/jira/browse/KAFKA-16137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-16137.
-
Fix Version/s: 3.8.0
Resolution: Fixed
merged the PR to trunk.
>
[
https://issues.apache.org/jira/browse/KAFKA-15811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15811.
-
Fix Version/s: 3.8.0
Resolution: Fixed
merged the PR to trunk.
> implement capturing client
[
https://issues.apache.org/jira/browse/KAFKA-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807374#comment-17807374
]
Jun Rao commented on KAFKA-15863:
-
[~apoorvmittal10] : If we only hit the push interval based
[
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://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://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}}
[
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}}
[
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
[
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
[
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-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
[
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://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791367#comment-17791367
]
Jun Rao commented on KAFKA-15950:
-
cc [~soarez]
> CommunicationEvent should be scheduled with
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-15674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778835#comment-17778835
]
Jun Rao commented on KAFKA-15674:
-
For context, [https://github.com/apache/kafka/pull/9220] was the
[
https://issues.apache.org/jira/browse/KAFKA-15401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778807#comment-17778807
]
Jun Rao commented on KAFKA-15401:
-
[~nickstery] : Thanks for reporting this issue. I am wondering how a
[
https://issues.apache.org/jira/browse/KAFKA-15651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15651.
-
Resolution: Not A Problem
> Investigate auto commit guarantees during Consumer.assign()
>
[
https://issues.apache.org/jira/browse/KAFKA-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15582.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk
> Clean shutdown detection,
[
https://issues.apache.org/jira/browse/KAFKA-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14960.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk.
> Metadata Request Manager and
[
https://issues.apache.org/jira/browse/KAFKA-15306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15306.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk
> Integrate committed offsets
[
https://issues.apache.org/jira/browse/KAFKA-15163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15163.
-
Fix Version/s: 3.7.0
Resolution: Fixed
This is covered in
[
https://issues.apache.org/jira/browse/KAFKA-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15115.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk
> Implement resetPositions
[
https://issues.apache.org/jira/browse/KAFKA-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-9800.
Fix Version/s: 3.7.0
Resolution: Fixed
Merged [https://github.com/apache/kafka/pull/14111] to
[
https://issues.apache.org/jira/browse/KAFKA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-15081.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk
> Implement new consumer
[
https://issues.apache.org/jira/browse/KAFKA-14965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14965.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk
> Introduce OffsetsRequestManager
[
https://issues.apache.org/jira/browse/KAFKA-14875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14875.
-
Fix Version/s: 3.7.0
Resolution: Fixed
merged the PR to trunk
> Implement Wakeup()
>
[
https://issues.apache.org/jira/browse/KAFKA-14950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14950.
-
Fix Version/s: 3.6.0
Resolution: Fixed
merged the PR to trunk.
> Implement assign() and
[
https://issues.apache.org/jira/browse/KAFKA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731375#comment-17731375
]
Jun Rao commented on KAFKA-15046:
-
The potential issue with moving the LeaderEpochFile flushing to an
[
https://issues.apache.org/jira/browse/KAFKA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731119#comment-17731119
]
Jun Rao commented on KAFKA-15046:
-
[~ocadaruma] : Thanks for identifying the problem. Another way to
[
https://issues.apache.org/jira/browse/KAFKA-14966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14966.
-
Fix Version/s: 3.6.0
Resolution: Fixed
Merged the PR to trunk.
> Extract reusable common logic
Jun Rao created KAFKA-15058:
---
Summary: Improve the accuracy of Histogram in client metric
Key: KAFKA-15058
URL: https://issues.apache.org/jira/browse/KAFKA-15058
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-14561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720717#comment-17720717
]
Jun Rao edited comment on KAFKA-14561 at 5/9/23 12:24 AM:
--
The PR was reverted
[
https://issues.apache.org/jira/browse/KAFKA-14561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-14561:
Fix Version/s: 3.6.0
(was: 3.5.0)
The PR was reverted in 3.5 branch. Updated the
[
https://issues.apache.org/jira/browse/KAFKA-14892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715193#comment-17715193
]
Jun Rao commented on KAFKA-14892:
-
Sounds good to me. Including storage in the package name probably
[
https://issues.apache.org/jira/browse/KAFKA-14561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14561.
-
Fix Version/s: 3.5.0
Resolution: Fixed
merged the PR to trunk.
> Improve transactions
[
https://issues.apache.org/jira/browse/KAFKA-14617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14617.
-
Fix Version/s: 3.5.0
Resolution: Fixed
merged all PRs to trunk.
> Replicas with stale broker
[
https://issues.apache.org/jira/browse/KAFKA-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14685.
-
Fix Version/s: 3.5.0
Resolution: Fixed
merged the PR to trunk.
> TierStateMachine interface for
[
https://issues.apache.org/jira/browse/KAFKA-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-14685:
---
Assignee: Matthew Wong
> TierStateMachine interface for building remote aux log
>
[
https://issues.apache.org/jira/browse/KAFKA-9087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655153#comment-17655153
]
Jun Rao commented on KAFKA-9087:
[~chia7712] : Thanks for the explanation. Great find! I agree that this
[
https://issues.apache.org/jira/browse/KAFKA-9087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651012#comment-17651012
]
Jun Rao commented on KAFKA-9087:
[~chia7712] : Thanks for the update. About the race condition. I am
[
https://issues.apache.org/jira/browse/KAFKA-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-10432:
---
Assignee: Lucas Bradstreet
> LeaderEpochCache is incorrectly recovered on segment recovery for
[
https://issues.apache.org/jira/browse/KAFKA-12736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-12736.
-
Fix Version/s: 3.0.0
Assignee: Lucas Bradstreet
Resolution: Fixed
> KafkaProducer.flush
[
https://issues.apache.org/jira/browse/KAFKA-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13369.
-
Fix Version/s: 3.5.0
Resolution: Fixed
merged the PR to trunk.
> Follower fetch protocol
[
https://issues.apache.org/jira/browse/KAFKA-14303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14303.
-
Fix Version/s: 3.4.0
3.3.2
Resolution: Fixed
Merged the PR to 3.3 and trunk.
[
https://issues.apache.org/jira/browse/KAFKA-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17619908#comment-17619908
]
Jun Rao commented on KAFKA-10760:
-
A potential solution is to implement the time based segment rolling
[
https://issues.apache.org/jira/browse/KAFKA-14321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14321.
-
Resolution: Duplicate
This actually duplicates KAFKA-10760. Closing this one.
> max.compaction.lag.ms
[
https://issues.apache.org/jira/browse/KAFKA-14321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17619904#comment-17619904
]
Jun Rao commented on KAFKA-14321:
-
A potential solution is to implement the time based segment rolling
Jun Rao created KAFKA-14321:
---
Summary: max.compaction.lag.ms is not enforced accurately
Key: KAFKA-14321
URL: https://issues.apache.org/jira/browse/KAFKA-14321
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-4545.
Fix Version/s: 3.1.0
Resolution: Fixed
This is fixed in KAFKA-8522.
> tombstone needs to be
[
https://issues.apache.org/jira/browse/KAFKA-14156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14156.
-
Assignee: Artem Livshits
Resolution: Fixed
Merged the PR to 3.3 and trunk.
> Built-in
[
https://issues.apache.org/jira/browse/KAFKA-13868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570964#comment-17570964
]
Jun Rao commented on KAFKA-13868:
-
Thanks, [~mimaison]. I see it now.
> Website updates to satisfy
[
https://issues.apache.org/jira/browse/KAFKA-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569563#comment-17569563
]
Jun Rao edited comment on KAFKA-13700 at 7/21/22 5:04 PM:
--
Interesting. So the
[
https://issues.apache.org/jira/browse/KAFKA-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569563#comment-17569563
]
Jun Rao commented on KAFKA-13700:
-
Interesting. So the CRC validation passes with DumpLogSegments, but
[
https://issues.apache.org/jira/browse/KAFKA-13868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569525#comment-17569525
]
Jun Rao commented on KAFKA-13868:
-
[~mimaison] : You mentioned "As per the email sent to the PMC, all
[
https://issues.apache.org/jira/browse/KAFKA-14020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-14020.
-
Resolution: Fixed
merged the PR to 3.3.
> Performance regression in Producer
>
[
https://issues.apache.org/jira/browse/KAFKA-12901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566418#comment-17566418
]
Jun Rao commented on KAFKA-12901:
-
[~suriyav] : Thanks for the reply. We recently fixed
[
https://issues.apache.org/jira/browse/KAFKA-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566412#comment-17566412
]
Jun Rao commented on KAFKA-13953:
-
[~doguscan] : It's possible that a Kafka bug caused the corruption.
[
https://issues.apache.org/jira/browse/KAFKA-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565138#comment-17565138
]
Jun Rao commented on KAFKA-13953:
-
[~doguscan] : The broker verifies the batch level CRC before
[
https://issues.apache.org/jira/browse/KAFKA-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564386#comment-17564386
]
Jun Rao commented on KAFKA-13953:
-
[~doguscan] : Interesting. Do all replicas have the identical
[
https://issues.apache.org/jira/browse/KAFKA-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17546196#comment-17546196
]
Jun Rao commented on KAFKA-13953:
-
[~abasilbr] : If you have multiple replicas, it's unlikely all
[
https://issues.apache.org/jira/browse/KAFKA-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13803.
-
Fix Version/s: 3.3.0
Resolution: Fixed
merged the PR to trunk
> Refactor Leader API Access
>
[
https://issues.apache.org/jira/browse/KAFKA-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17545575#comment-17545575
]
Jun Rao commented on KAFKA-13953:
-
[~abasilbr] : This could be caused by data corruption on the broker.
[
https://issues.apache.org/jira/browse/KAFKA-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-10888.
-
Fix Version/s: 3.3.0
Resolution: Fixed
merged the PR to trunk. Thanks [~alivshits] for the
[
https://issues.apache.org/jira/browse/KAFKA-13815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13815.
-
Fix Version/s: 3.3.0
Resolution: Fixed
merged the PR to trunk
> Avoid reinitialization for a
[
https://issues.apache.org/jira/browse/KAFKA-12841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-12841:
---
Fix Version/s: 3.2.0
Assignee: Philip Nee (was: Kirk True)
Resolution: Fixed
[
https://issues.apache.org/jira/browse/KAFKA-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13448.
-
Fix Version/s: 3.2.0
Assignee: Philip Nee
Resolution: Fixed
merged
[
https://issues.apache.org/jira/browse/KAFKA-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519194#comment-17519194
]
Jun Rao commented on KAFKA-9296:
[~vongosling] : It would be useful to provide a bit more detail on when
[
https://issues.apache.org/jira/browse/KAFKA-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13687.
-
Fix Version/s: 3.3.0
Resolution: Fixed
merged the PR to trunk.
> Limit number of batches when
[
https://issues.apache.org/jira/browse/KAFKA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515532#comment-17515532
]
Jun Rao edited comment on KAFKA-13773 at 3/31/22 7:25 PM:
--
[~Timelad] : Thanks
[
https://issues.apache.org/jira/browse/KAFKA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515532#comment-17515532
]
Jun Rao commented on KAFKA-13773:
-
[~Timelad] : Thanks for the log. This does seem to be a real issue.
[
https://issues.apache.org/jira/browse/KAFKA-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-12875.
-
Fix Version/s: 3.3.0
Assignee: Yu Yang
Resolution: Fixed
Merged to trunk.
> Change Log
[
https://issues.apache.org/jira/browse/KAFKA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514888#comment-17514888
]
Jun Rao commented on KAFKA-13773:
-
[~Timelad] : I checked kafka-0-2.8.0-before-fail.log
[
https://issues.apache.org/jira/browse/KAFKA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514808#comment-17514808
]
Jun Rao commented on KAFKA-13773:
-
[~Timelad] : Thanks for the additional logs. I took a quick look at
[
https://issues.apache.org/jira/browse/KAFKA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514245#comment-17514245
]
Jun Rao commented on KAFKA-13773:
-
[~Timelad] : Thanks for filing the jira. I ran the following tool on
[
https://issues.apache.org/jira/browse/KAFKA-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507142#comment-17507142
]
Jun Rao commented on KAFKA-13744:
-
[~jeqo] : Thanks for reporting this issue. It seems that the tags are
[
https://issues.apache.org/jira/browse/KAFKA-13723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503854#comment-17503854
]
Jun Rao commented on KAFKA-13723:
-
[~xiongqiwu] : Thanks for the explanation. Make sense. So, this is
[
https://issues.apache.org/jira/browse/KAFKA-13723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13723.
-
Resolution: Not A Problem
> max.compaction.lag.ms implemented incorrectly
>
[
https://issues.apache.org/jira/browse/KAFKA-13723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503813#comment-17503813
]
Jun Rao commented on KAFKA-13723:
-
[~xiongqiwu] and [~jjkoshy] : Could you check if this is a real
Jun Rao created KAFKA-13723:
---
Summary: max.compaction.lag.ms implemented incorrectly
Key: KAFKA-13723
URL: https://issues.apache.org/jira/browse/KAFKA-13723
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-10690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503785#comment-17503785
]
Jun Rao commented on KAFKA-10690:
-
[~ocadaruma] : Thanks for filing the jira. Have you tried enabling
[
https://issues.apache.org/jira/browse/KAFKA-12901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499138#comment-17499138
]
Jun Rao commented on KAFKA-12901:
-
[~suriyav] : Did you see the same log error as in KAFKA-7987? If not,
[
https://issues.apache.org/jira/browse/KAFKA-13461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497763#comment-17497763
]
Jun Rao commented on KAFKA-13461:
-
Basically, when there is no JAAS configured for ZK client and the ZK
[
https://issues.apache.org/jira/browse/KAFKA-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13407.
-
Resolution: Fixed
> Kafka controller out of service after ZK leader restart
>
[
https://issues.apache.org/jira/browse/KAFKA-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497760#comment-17497760
]
Jun Rao commented on KAFKA-13407:
-
[~Olsson] : Thanks for the reply. I think we fixed this issue in
[
https://issues.apache.org/jira/browse/KAFKA-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13603.
-
Fix Version/s: 3.2.0
Resolution: Fixed
merged the PR to trunk.
> empty active segment can
1 - 100 of 481 matches
Mail list logo
