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:
[
https://issues.apache.org/jira/browse/KAFKA-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745672#comment-16745672
]
Jun Rao commented on KAFKA-7836:
[~lindong], it seems that we could call zkClient.propagateLogDirEvent
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
[
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
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:
[
https://issues.apache.org/jira/browse/KAFKA-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744272#comment-16744272
]
Jun Rao commented on KAFKA-7829:
[~lindong], could you verify if this is inaccurate?
> Inaccurate
[
https://issues.apache.org/jira/browse/KAFKA-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736415#comment-16736415
]
Jun Rao commented on KAFKA-7786:
Great find, Anna. About the fix. I am not sure that we need the protocol
[
https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722217#comment-16722217
]
Jun Rao commented on KAFKA-7297:
[~lindong], good points. The current implementation is not causing
[
https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721960#comment-16721960
]
Jun Rao commented on KAFKA-7297:
[~lindong], Ismael pointed out that ConcurrentSkipListMap supports
[
https://issues.apache.org/jira/browse/KAFKA-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721607#comment-16721607
]
Jun Rao commented on KAFKA-7681:
[~mgharat], Meter is calculated by (accumulated values / time of the
[
https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720819#comment-16720819
]
Jun Rao commented on KAFKA-2729:
[~murri71], my earlier comment was referring to that we fixed the
[
https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720710#comment-16720710
]
Jun Rao commented on KAFKA-7297:
To follow up on that, another related issue is that currently, we are
[
https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719228#comment-16719228
]
Jun Rao commented on KAFKA-5692:
[~tombentley], that's good to know. Thanks for your help.
> Refactor
[
https://issues.apache.org/jira/browse/KAFKA-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718002#comment-16718002
]
Jun Rao commented on KAFKA-7713:
io-wait-ratio is calculated as the ratio of accumulated selector waiting
[
https://issues.apache.org/jira/browse/KAFKA-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716273#comment-16716273
]
Jun Rao commented on KAFKA-7680:
[~NIzhikov], thanks for your interest. Feel free to assign the Jira to
[
https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713395#comment-16713395
]
Jun Rao commented on KAFKA-5692:
[~tombentley], thanks for contributing the PR. Would be still 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.
>
[
https://issues.apache.org/jira/browse/KAFKA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709589#comment-16709589
]
Jun Rao commented on KAFKA-7704:
[~yuyang08], could you try the PR and see if it fixes the issue? Thanks,
[
https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709539#comment-16709539
]
Jun Rao commented on KAFKA-2729:
We fixed another issue that can fail the re-creation of the broker
[
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
[
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
[
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.
>
[
https://issues.apache.org/jira/browse/KAFKA-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702176#comment-16702176
]
Jun Rao commented on KAFKA-7681:
Hi, [~mgharat],
The Broker Topic metrics only collect the byte
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:
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:
[
https://issues.apache.org/jira/browse/KAFKA-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701084#comment-16701084
]
Jun Rao commented on KAFKA-7680:
One way to fix this is the following. We already include the expected
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=16692047#comment-16692047
]
Jun Rao commented on KAFKA-4277:
[~birger] : Hmm, according to
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667977#comment-16667977
]
Jun Rao commented on KAFKA-7481:
I agree that introducing a new config probably needs more thought.
[
https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667914#comment-16667914
]
Jun Rao commented on KAFKA-7165:
[~pachilo], your PR actually looks reasonable for addressing the issue
[
https://issues.apache.org/jira/browse/KAFKA-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665737#comment-16665737
]
Jun Rao commented on KAFKA-7557:
To improve this, instead of calling
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
[
https://issues.apache.org/jira/browse/KAFKA-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662538#comment-16662538
]
Jun Rao commented on KAFKA-7538:
[~rsivaram], thanks for the analysis. I agree that approach 2) is
[
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
[
https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650798#comment-16650798
]
Jun Rao commented on KAFKA-7504:
The case that Allen described is when a follower is fetching both
[
https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16649546#comment-16649546
]
Jun Rao commented on KAFKA-7504:
[~kawamuray], thanks for the jira. Great find. Simple, but yet effective
[
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
[
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
[
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
[
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
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615492#comment-16615492
]
Jun Rao commented on KAFKA-7408:
It does seem that truncating to LSO handles unclean leader election
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599003#comment-16599003
]
Jun Rao commented on KAFKA-7366:
[~ijuma], it might be debatable. However, if all other topic level
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
[
https://issues.apache.org/jira/browse/KAFKA-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595702#comment-16595702
]
Jun Rao commented on KAFKA-7287:
[~omkreddy], thanks for the patch. I merged the PR to trunk and 2.0. It
[
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=16588220#comment-16588220
]
Jun Rao commented on KAFKA-6753:
[~luwang], that sounds good too. To make tracking easier, perhaps it's
[
https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588026#comment-16588026
]
Jun Rao commented on KAFKA-6753:
[~luwang], we could consider removing this metric, but it probably
[
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
[
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
[
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
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
[
https://issues.apache.org/jira/browse/KAFKA-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551864#comment-16551864
]
Jun Rao commented on KAFKA-7152:
Thanks for reporting the issue. A few things.
# Not sure if the
[
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.
>
[
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
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495306#comment-16495306
]
Jun Rao commented on KAFKA-3042:
Interesting. Do you have the controller and the state-change log around
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493976#comment-16493976
]
Jun Rao commented on KAFKA-3042:
We fixed KAFKA-2729 in 1.1.0 that could lead to Cached zkVersion.
>
[
https://issues.apache.org/jira/browse/KAFKA-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491723#comment-16491723
]
Jun Rao commented on KAFKA-6952:
Hmm, could you run bin/kafka-run-class.sh kafka.tools.DumpLogSegments on
[
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
[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491376#comment-16491376
]
Jun Rao commented on KAFKA-6937:
[~klafferty], thanks for testing this out. Yes, the reason for including
[
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
[
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.
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
[
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
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
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=16457130#comment-16457130
]
Jun Rao commented on KAFKA-6834:
To fix this, we need to handle the cleaner buffer to grow up to the size
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
[
https://issues.apache.org/jira/browse/KAFKA-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434646#comment-16434646
]
Jun Rao commented on KAFKA-6780:
The fix is probably to further bound firstUncleanableDirtyOffset by the
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
[
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
[
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
[
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
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-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
[
https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390727#comment-16390727
]
Jun Rao commented on KAFKA-6624:
[~lindong], do you think this is an issue? Thanks.
> log segment
[
https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390572#comment-16390572
]
Jun Rao commented on KAFKA-6624:
One way to fix this is to add a flag for a log segment to be deleted.
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
[
https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387125#comment-16387125
]
Jun Rao commented on KAFKA-3978:
Agreed. For 1) we could add an assertion. For 2), if we detect that we
[
https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366546#comment-16366546
]
Jun Rao commented on KAFKA-4277:
[~nico.meyer], do you know if the conflicting ephemeral node was there
[
https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364973#comment-16364973
]
Jun Rao commented on KAFKA-6549:
We can fix this issue with the updated version in
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352719#comment-16352719
]
Jun Rao commented on KAFKA-6254:
Some perf results from [~afalko].
Without patch @46k partitions:
[
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
301 - 400 of 488 matches
Mail list logo