[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ 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

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ 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 

[jira] [Commented] (KAFKA-7681) new metric for request thread utilization by request type

[ 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

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ 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

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ 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

[jira] [Commented] (KAFKA-5692) Refactor PreferredReplicaLeaderElectionCommand to use AdminClient

[ 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

[jira] [Commented] (KAFKA-7713) producer io-wait-ratio > 1

[ 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

[jira] [Commented] (KAFKA-7680) fetching a refilled chunk of log can cause log divergence

[ 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

[jira] [Commented] (KAFKA-5692) Refactor PreferredReplicaLeaderElectionCommand to use AdminClient

[ 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

[jira] [Resolved] (KAFKA-7704) kafka.server.ReplicaFetechManager.MaxLag.Replica metric is reported incorrectly

[ 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. >

[jira] [Commented] (KAFKA-7704) kafka.server.ReplicaFetechManager.MaxLag.Replica metric is reported incorrectly

[ 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,

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ 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

[jira] [Resolved] (KAFKA-1120) Controller could miss a broker state change

[ 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 

[jira] [Resolved] (KAFKA-7235) Use brokerZkNodeVersion to prevent broker from processing outdated controller request

[ 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

[jira] [Resolved] (KAFKA-7449) Kafka console consumer is not sending topic to deserializer

[ 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. >

[jira] [Commented] (KAFKA-7681) new metric for request thread utilization by request type

[ 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

[jira] [Created] (KAFKA-7682) turning on request logging for a subset of request types

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:

[jira] [Created] (KAFKA-7681) new metric for request thread utilization by request 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:

[jira] [Commented] (KAFKA-7680) fetching a refilled chunk of log can cause log divergence

[ 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

[jira] [Created] (KAFKA-7680) fetching a refilled chunk of log can cause log divergence

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

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ 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

[jira] [Resolved] (KAFKA-7412) Bug prone response from producer.send(ProducerRecord, Callback) if Kafka broker is not running

[ 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

[jira] [Resolved] (KAFKA-7537) Only include live brokers in the UpdateMetadataRequest sent to existing brokers if there is no change in the partition states

[ 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

[jira] [Commented] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ 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.

[jira] [Commented] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ 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

[jira] [Commented] (KAFKA-7557) optimize LogManager.truncateFullyAndStartAt()

[ 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

[jira] [Created] (KAFKA-7557) optimize LogManager.truncateFullyAndStartAt()

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

[jira] [Commented] (KAFKA-7538) Improve locking model used to update ISRs and HW

[ 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

[jira] [Updated] (KAFKA-7299) batch LeaderAndIsr requests during auto preferred leader election

[ 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

[jira] [Commented] (KAFKA-7504) Broker performance degradation caused by call of sendfile reading disk in network thread

[ 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

[jira] [Commented] (KAFKA-7504) Broker performance degradation caused by call of sendfile reading disk in network thread

[ 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

[jira] [Resolved] (KAFKA-7482) LeaderAndIsrRequest should be sent to the shutting down broker

[ 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

[jira] [Resolved] (KAFKA-3097) Acls for PrincipalType User are case sensitive

[ 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

[jira] [Resolved] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

[ 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

[jira] [Resolved] (KAFKA-7215) Improve LogCleaner behavior on error

[ 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

[jira] [Created] (KAFKA-7482) LeaderAndIsrRequest should be sent to the shutting down broker

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

[jira] [Resolved] (KAFKA-7216) Exception while running kafka-acls.sh from 1.0 env on target Kafka env with 1.1.1

[ 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

[jira] [Resolved] (KAFKA-7400) Compacted topic segments that precede the log start offset are not cleaned up

[ 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

[jira] [Commented] (KAFKA-7408) Truncate to LSO on unclean leader election

[ 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

[jira] [Resolved] (KAFKA-7117) Allow AclCommand to use AdminClient API

[ 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

[jira] [Resolved] (KAFKA-7287) Set open ACL permissions for old consumer znode path

[ 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

[jira] [Commented] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

[ 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

[jira] [Created] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

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

[jira] [Commented] (KAFKA-7287) Set open ACL permissions for old consumer znode path

[ 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

[jira] [Resolved] (KAFKA-6343) OOM as the result of creation of 5k topics

[ 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.

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ 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

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ 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

[jira] [Resolved] (KAFKA-6753) Speed up event processing on the controller

[ 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

[jira] [Resolved] (KAFKA-6835) Enable topic unclean leader election to be enabled without controller change

[ 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

[jira] [Resolved] (KAFKA-7299) batch LeaderAndIsr requests during auto preferred leader election

[ 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

[jira] [Created] (KAFKA-7299) batch LeaderAndIsr requests during auto preferred leader election

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

[jira] [Commented] (KAFKA-7152) replica should be in-sync if its LEO equals leader's LEO

[ 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

[jira] [Resolved] (KAFKA-7064) "Unexpected resource type GROUP" when describing broker configs using latest admin client

[ 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. >

[jira] [Resolved] (KAFKA-7010) Rename ResourceNameType.ANY to MATCH

[ 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 >

[jira] [Updated] (KAFKA-7007) 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: --- Description: Relating to one of the outstanding work items in PR

[jira] [Resolved] (KAFKA-7007) 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 resolved KAFKA-7007. Resolution: Fixed merged the PR to trunk and 2.0 branch. > Use JSON for /kafka-acl-extended-changes path

[jira] [Updated] (KAFKA-7007) 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

[jira] [Resolved] (KAFKA-7005) Remove duplicate Java Resource 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. >

[jira] [Resolved] (KAFKA-7006) Remove duplicate Scala ResourceNameType 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

[jira] [Resolved] (KAFKA-7011) Investigate if its possible to drop the ResourceNameType field from Java Resource 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

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ 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

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ 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. >

[jira] [Commented] (KAFKA-6952) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ 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

[jira] [Resolved] (KAFKA-6937) 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 resolved KAFKA-6937. Resolution: Fixed Fix Version/s: 1.1.1 1.0.2 2.0.0 Merged the

[jira] [Commented] (KAFKA-6937) 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=16491376#comment-16491376 ] Jun Rao commented on KAFKA-6937: [~klafferty], thanks for testing this out. Yes, the reason for including

[jira] [Updated] (KAFKA-6937) 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: --- Component/s: core > In-sync replica delayed during fetch if replica throttle is exceeded >

[jira] [Updated] (KAFKA-6937) 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

[jira] [Updated] (KAFKA-6937) 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: --- Description: When replication throttling is enabled, in-sync replica's traffic should never be throttled.

[jira] [Created] (KAFKA-6937) In-sync replica delayed during fetch if replica throttle is exceeded

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

[jira] [Resolved] (KAFKA-6361) Fast leader fail over can lead to log divergence between leader and follower

[ 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

[jira] [Created] (KAFKA-6858) Log.truncateTo() may truncate to an earlier offset than requested

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

[jira] [Created] (KAFKA-6857) LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH explicitly

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

[jira] [Commented] (KAFKA-6834) log cleaner should handle the case when the size of a message set is larger than the max message size

[ 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

[jira] [Created] (KAFKA-6834) log cleaner should handle the case when the size of a message set is larger than the max message 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

[jira] [Resolved] (KAFKA-6650) The controller should be able to handle a partially deleted topic

[ 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

[jira] [Commented] (KAFKA-6780) log cleaner shouldn't clean messages beyond high watermark

[ 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

[jira] [Created] (KAFKA-6780) log cleaner shouldn't clean messages beyond high watermark

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

[jira] [Resolved] (KAFKA-6447) Add Delegation Token Operations to KafkaAdminClient

[ 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

[jira] [Resolved] (KAFKA-6752) Unclean leader election metric no longer working

[ 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

[jira] [Resolved] (KAFKA-5706) log the name of the error instead of the error code in response objects

[ 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

[jira] [Resolved] (KAFKA-3827) log.message.format.version should default to inter.broker.protocol.version

[ 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

[jira] [Created] (KAFKA-6760) responses not logged properly in controller

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

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

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

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

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390727#comment-16390727 ] Jun Rao commented on KAFKA-6624: [~lindong], do you think this is an issue? Thanks. > log segment

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

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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.

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

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

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

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387125#comment-16387125 ] Jun Rao commented on KAFKA-3978: Agreed. For 1) we could add an assertion. For 2), if we detect that we

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ 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

[jira] [Commented] (KAFKA-6549) Deadlock while processing Controller Events

[ 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 

[jira] [Resolved] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ 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

[jira] [Resolved] (KAFKA-6452) Add documentation for delegation token authentication mechanism

[ 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

[jira] [Commented] (KAFKA-6254) Introduce Incremental FetchRequests to Increase Partition Scalability

[ 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:

[jira] [Resolved] (KAFKA-6254) Introduce Incremental FetchRequests to Increase Partition Scalability

[ 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

[jira] [Commented] (KAFKA-6469) ISR change notification queue can prevent controller from making progress

[ https://issues.apache.org/jira/browse/KAFKA-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352667#comment-16352667 ] Jun Rao commented on KAFKA-6469: [~ambroff], thanks for reporting this. Is the # of children in the

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341863#comment-16341863 ] Jun Rao commented on KAFKA-2729: The problem that we fixed related to this jira is KAFKA-5642. Previously,

[jira] [Commented] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

[ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340295#comment-16340295 ] Jun Rao commented on KAFKA-5886: https://github.com/apache/kafka/pull/3849 > Introduce

[jira] [Commented] (KAFKA-6254) Introduce Incremental FetchRequests to Increase Partition Scalability

[ https://issues.apache.org/jira/browse/KAFKA-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339830#comment-16339830 ] Jun Rao commented on KAFKA-6254: https://github.com/apache/kafka/pull/4418 > Introduce Incremental

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293473#comment-16293473 ] Jun Rao commented on KAFKA-3410: [~wushujames], yes, KAFKA-1211 should help address this. Do you want to

[jira] [Commented] (KAFKA-6361) Fast leader fail over can lead to log divergence between leader and follower

[ https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291812#comment-16291812 ] Jun Rao commented on KAFKA-6361: [~hachikuji], thanks for the info. The problem in the description can

[jira] [Commented] (KAFKA-6361) Fast leader fail over can lead to log divergence between leader and follower

[ https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290252#comment-16290252 ] Jun Rao commented on KAFKA-6361: Was unclean leader election enabled in this case? When broker B takes

<    1   2   3   4   5   >