[jira] [Resolved] (KAFKA-5367) Producer should not expiry topic from metadata cache if accumulator still has data for this topic

[ https://issues.apache.org/jira/browse/KAFKA-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5367. - Resolution: Invalid > Producer should not expiry topic from metadata cache if accumulator still has > dat

[jira] [Created] (KAFKA-5521) Support replicas movement between log directories (KIP-113)

Dong Lin created KAFKA-5521: --- Summary: Support replicas movement between log directories (KIP-113) Key: KAFKA-5521 URL: https://issues.apache.org/jira/browse/KAFKA-5521 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-5521) Support replicas movement between log directories (KIP-113)

[ https://issues.apache.org/jira/browse/KAFKA-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5521. - Resolution: Duplicate Duplicate of https://issues.apache.org/jira/browse/KAFKA-5163 > Support replicas mo

[jira] [Created] (KAFKA-5542) Improve Java doc for LeaderEpochFileCache.endOffsetFor()

Dong Lin created KAFKA-5542: --- Summary: Improve Java doc for LeaderEpochFileCache.endOffsetFor() Key: KAFKA-5542 URL: https://issues.apache.org/jira/browse/KAFKA-5542 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5544) The LastStableOffsetLag metric should be removed when partition is deleted

Dong Lin created KAFKA-5544: --- Summary: The LastStableOffsetLag metric should be removed when partition is deleted Key: KAFKA-5544 URL: https://issues.apache.org/jira/browse/KAFKA-5544 Project: Kafka

[jira] [Created] (KAFKA-5626) Producer should be able to negotiate ProduceRequest version with broker

Dong Lin created KAFKA-5626: --- Summary: Producer should be able to negotiate ProduceRequest version with broker Key: KAFKA-5626 URL: https://issues.apache.org/jira/browse/KAFKA-5626 Project: Kafka

[jira] [Created] (KAFKA-5627) Reduce classes needed for LeaderAndIsrPartitionState and MetadataPartitionState

Dong Lin created KAFKA-5627: --- Summary: Reduce classes needed for LeaderAndIsrPartitionState and MetadataPartitionState Key: KAFKA-5627 URL: https://issues.apache.org/jira/browse/KAFKA-5627 Project: Kafka

[jira] [Created] (KAFKA-5694) Add ChangeReplicaDirRequest and DescribeReplicaDirRequest (KIP-113)

Dong Lin created KAFKA-5694: --- Summary: Add ChangeReplicaDirRequest and DescribeReplicaDirRequest (KIP-113) Key: KAFKA-5694 URL: https://issues.apache.org/jira/browse/KAFKA-5694 Project: Kafka Issu

[jira] [Created] (KAFKA-5695) Test DeleteRecordsRequest in AuthorizerIntegrationTest

Dong Lin created KAFKA-5695: --- Summary: Test DeleteRecordsRequest in AuthorizerIntegrationTest Key: KAFKA-5695 URL: https://issues.apache.org/jira/browse/KAFKA-5695 Project: Kafka Issue Type: Improv

[jira] [Created] (KAFKA-5710) KafkaAdminClient should remove inflight call correctly after response is received

Dong Lin created KAFKA-5710: --- Summary: KafkaAdminClient should remove inflight call correctly after response is received Key: KAFKA-5710 URL: https://issues.apache.org/jira/browse/KAFKA-5710 Project: Kafka

[jira] [Created] (KAFKA-5759) Allow user to specify relative path as log directory

Dong Lin created KAFKA-5759: --- Summary: Allow user to specify relative path as log directory Key: KAFKA-5759 URL: https://issues.apache.org/jira/browse/KAFKA-5759 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5767) Kafka server should halt if IBP < 1.0.0 and there is log directory failure

Dong Lin created KAFKA-5767: --- Summary: Kafka server should halt if IBP < 1.0.0 and there is log directory failure Key: KAFKA-5767 URL: https://issues.apache.org/jira/browse/KAFKA-5767 Project: Kafka

[jira] [Created] (KAFKA-5812) Represent logDir with case class where absolute path is required

Dong Lin created KAFKA-5812: --- Summary: Represent logDir with case class where absolute path is required Key: KAFKA-5812 URL: https://issues.apache.org/jira/browse/KAFKA-5812 Project: Kafka Issue T

[jira] [Created] (KAFKA-5829) Speedup broker startup after unclean shutdown by reducing unnecessary snapshot files deletion

Dong Lin created KAFKA-5829: --- Summary: Speedup broker startup after unclean shutdown by reducing unnecessary snapshot files deletion Key: KAFKA-5829 URL: https://issues.apache.org/jira/browse/KAFKA-5829 Pro

[jira] [Created] (KAFKA-5843) Mx4jLoader.maybeLoad should only be executed if kafka_mx4jenable is set to true

Dong Lin created KAFKA-5843: --- Summary: Mx4jLoader.maybeLoad should only be executed if kafka_mx4jenable is set to true Key: KAFKA-5843 URL: https://issues.apache.org/jira/browse/KAFKA-5843 Project: Kafka

[jira] [Created] (KAFKA-5845) KafkaController should send LeaderAndIsrRequest to brokers which starts very soon after shutdown

Dong Lin created KAFKA-5845: --- Summary: KafkaController should send LeaderAndIsrRequest to brokers which starts very soon after shutdown Key: KAFKA-5845 URL: https://issues.apache.org/jira/browse/KAFKA-5845

[jira] [Created] (KAFKA-5864) ReplicaFetcherThread.processPartitionData() should throw KafkaStorageException if replica is offline

Dong Lin created KAFKA-5864: --- Summary: ReplicaFetcherThread.processPartitionData() should throw KafkaStorageException if replica is offline Key: KAFKA-5864 URL: https://issues.apache.org/jira/browse/KAFKA-5864

[jira] [Resolved] (KAFKA-5845) KafkaController should send LeaderAndIsrRequest to broker which starts very soon after shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5845. - Resolution: Won't Fix > KafkaController should send LeaderAndIsrRequest to broker which starts very > soo

[jira] [Created] (KAFKA-5877) Controller should only update reassignment znode if there is change in the reassignment data

Dong Lin created KAFKA-5877: --- Summary: Controller should only update reassignment znode if there is change in the reassignment data Key: KAFKA-5877 URL: https://issues.apache.org/jira/browse/KAFKA-5877 Proj

[jira] [Created] (KAFKA-5878) Add sensor for queue size of the controller-event-thread

Dong Lin created KAFKA-5878: --- Summary: Add sensor for queue size of the controller-event-thread Key: KAFKA-5878 URL: https://issues.apache.org/jira/browse/KAFKA-5878 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5879) Controller should read the latest IsrChangeNotification znodes when handling IsrChangeNotification event

Dong Lin created KAFKA-5879: --- Summary: Controller should read the latest IsrChangeNotification znodes when handling IsrChangeNotification event Key: KAFKA-5879 URL: https://issues.apache.org/jira/browse/KAFKA-5879

[jira] [Created] (KAFKA-3908) Set SendBufferSize for socket used by Processor

Dong Lin created KAFKA-3908: --- Summary: Set SendBufferSize for socket used by Processor Key: KAFKA-3908 URL: https://issues.apache.org/jira/browse/KAFKA-3908 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511392#comment-14511392 ] Dong Lin commented on KAFKA-1936: - Thanks! I will work on this ticket. On Fri, Apr 24, 20

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Status: Patch Available (was: Open) > Track offset commit requests separately from produce requests > -

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Attachment: KAFKA-1936.patch > Track offset commit requests separately from produce requests > -

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512768#comment-14512768 ] Dong Lin commented on KAFKA-1936: - Created reviewboard https://reviews.apache.org/r/33557/

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Attachment: KAFKA-1936_2015-04-26_21:20:28.patch > Track offset commit requests separately from produce requ

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513503#comment-14513503 ] Dong Lin commented on KAFKA-1936: - Updated reviewboard https://reviews.apache.org/r/33557/

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513508#comment-14513508 ] Dong Lin commented on KAFKA-1936: - Updated reviewboard https://reviews.apache.org/r/33557/

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Attachment: KAFKA-1936_2015-04-26_21:26:34.patch > Track offset commit requests separately from produce requ

[jira] [Commented] (KAFKA-2103) kafka.producer.AsyncProducerTest failure.

[ https://issues.apache.org/jira/browse/KAFKA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513558#comment-14513558 ] Dong Lin commented on KAFKA-2103: - Of course. Let me work on this ticket. > kafka.produce

[jira] [Commented] (KAFKA-2103) kafka.producer.AsyncProducerTest failure.

[ https://issues.apache.org/jira/browse/KAFKA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514983#comment-14514983 ] Dong Lin commented on KAFKA-2103: - This test case fails because a local process on Jiangji

[jira] [Commented] (KAFKA-2084) byte rate metrics per client ID (producer and consumer)

[ https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522757#comment-14522757 ] Dong Lin commented on KAFKA-2084: - Here is my 2 cents. I vote for your 2nd approach: Clien

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527454#comment-14527454 ] Dong Lin commented on KAFKA-1936: - Updated reviewboard https://reviews.apache.org/r/33557/

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Attachment: KAFKA-1936_2015-05-04_15:17:50.patch > Track offset commit requests separately from produce requ

[jira] [Created] (KAFKA-2171) System Test for Quotas

Dong Lin created KAFKA-2171: --- Summary: System Test for Quotas Key: KAFKA-2171 URL: https://issues.apache.org/jira/browse/KAFKA-2171 Project: Kafka Issue Type: Sub-task Reporter: Dong Li

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Attachment: KAFKA-1936_2015-05-12_07:32:07.patch > Track offset commit requests separately from produce requ

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539906#comment-14539906 ] Dong Lin commented on KAFKA-1936: - Updated reviewboard https://reviews.apache.org/r/33557/

[jira] [Commented] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539974#comment-14539974 ] Dong Lin commented on KAFKA-1936: - Updated reviewboard https://reviews.apache.org/r/33557/

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Attachment: KAFKA-1936_2015-05-12_08:02:32.patch > Track offset commit requests separately from produce requ

[jira] [Created] (KAFKA-2191) Measured rate should not be infinite

Dong Lin created KAFKA-2191: --- Summary: Measured rate should not be infinite Key: KAFKA-2191 URL: https://issues.apache.org/jira/browse/KAFKA-2191 Project: Kafka Issue Type: Bug Reporter

[jira] [Updated] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2191: Status: Patch Available (was: Open) > Measured rate should not be infinite > --

[jira] [Updated] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2191: Attachment: KAFKA-2191.patch > Measured rate should not be infinite > >

[jira] [Commented] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542135#comment-14542135 ] Dong Lin commented on KAFKA-2191: - Created reviewboard https://reviews.apache.org/r/34170/

[jira] [Updated] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2191: Attachment: KAFKA-2191_2015-05-13_15:32:15.patch > Measured rate should not be infinite > --

[jira] [Commented] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542851#comment-14542851 ] Dong Lin commented on KAFKA-2191: - Updated reviewboard https://reviews.apache.org/r/34170/

[jira] [Commented] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543329#comment-14543329 ] Dong Lin commented on KAFKA-2191: - Updated reviewboard https://reviews.apache.org/r/34170/

[jira] [Updated] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2191: Attachment: KAFKA-2191_2015-05-14_00:34:30.patch > Measured rate should not be infinite > --

[jira] [Updated] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2171: Attachment: KAFKA-2171.patch > System Test for Quotas > -- > > Key: KAFK

[jira] [Updated] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2171: Status: Patch Available (was: Open) > System Test for Quotas > -- > > K

[jira] [Commented] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562070#comment-14562070 ] Dong Lin commented on KAFKA-2171: - Created reviewboard https://reviews.apache.org/r/34742/

[jira] [Commented] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562074#comment-14562074 ] Dong Lin commented on KAFKA-2191: - Updated reviewboard https://reviews.apache.org/r/34170/

[jira] [Updated] (KAFKA-2191) Measured rate should not be infinite

[ https://issues.apache.org/jira/browse/KAFKA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2191: Attachment: KAFKA-2191_2015-05-27_17:28:41.patch > Measured rate should not be infinite > --

[jira] [Updated] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2171: Description: Initial setup and configuration: In all scenarios, we create the following entities and topic:

[jira] [Created] (KAFKA-2240) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

Dong Lin created KAFKA-2240: --- Summary: AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer) Key: KAFKA-2240 URL: https://issues.apache.org/jira/browse/KAFKA-2240 Project: Ka

[jira] [Created] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

Dong Lin created KAFKA-2241: --- Summary: AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer) Key: KAFKA-2241 URL: https://issues.apache.org/jira/browse/KAFKA-2241 Project: Ka

[jira] [Updated] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2241: Attachment: client.java server.java Run server before client. Then check if channel.read() w

[jira] [Resolved] (KAFKA-2240) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-2240. - Resolution: Duplicate > AbstractFetcherThread.shutdown() should not block on > ReadableByteChannel.read(b

[jira] [Closed] (KAFKA-2240) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin closed KAFKA-2240. --- Duplicate of KAFKA-2241. > AbstractFetcherThread.shutdown() should not block on > ReadableByteChannel.read(buffe

[jira] [Commented] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569988#comment-14569988 ] Dong Lin commented on KAFKA-2241: - Oh, I thought the first issue creation has failed. Tha

[jira] [Updated] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2241: Status: Patch Available (was: Open) > AbstractFetcherThread.shutdown() should not block on > ReadableByteC

[jira] [Commented] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570010#comment-14570010 ] Dong Lin commented on KAFKA-2241: - Created reviewboard https://reviews.apache.org/r/34965/

[jira] [Updated] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2241: Attachment: KAFKA-2241.patch > AbstractFetcherThread.shutdown() should not block on > ReadableByteChannel.r

[jira] [Updated] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2171: Description: Initial setup and configuration: In all scenarios, we create the following entities and topic:

[jira] [Updated] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2171: Attachment: KAFKA-2171.patch > System Test for Quotas > -- > > Key: KAFK

[jira] [Commented] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571464#comment-14571464 ] Dong Lin commented on KAFKA-2171: - Updated reviewboard https://reviews.apache.org/r/34742/

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

[ https://issues.apache.org/jira/browse/KAFKA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-1936: Resolution: Not A Problem Status: Resolved (was: Patch Available) After discussion we decided to ke

[jira] [Updated] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2241: Attachment: KAFKA-2241_2015-06-03_15:30:35.patch > AbstractFetcherThread.shutdown() should not block on > R

[jira] [Commented] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571766#comment-14571766 ] Dong Lin commented on KAFKA-2241: - Updated reviewboard https://reviews.apache.org/r/34965/

[jira] [Created] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

Dong Lin created KAFKA-4415: --- Summary: Reduce time to create and send MetadataUpdateRequest Key: KAFKA-4415 URL: https://issues.apache.org/jira/browse/KAFKA-4415 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

[ https://issues.apache.org/jira/browse/KAFKA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-4415: --- Assignee: Dong Lin > Reduce time to create and send MetadataUpdateRequest > -

[jira] [Created] (KAFKA-4420) Group StopReplicaRequests for partitions on the same broker into one StopReplicaRequest

Dong Lin created KAFKA-4420: --- Summary: Group StopReplicaRequests for partitions on the same broker into one StopReplicaRequest Key: KAFKA-4420 URL: https://issues.apache.org/jira/browse/KAFKA-4420 Project:

[jira] [Created] (KAFKA-4429) records-lag should be zero if FetchResponse is empty

Dong Lin created KAFKA-4429: --- Summary: records-lag should be zero if FetchResponse is empty Key: KAFKA-4429 URL: https://issues.apache.org/jira/browse/KAFKA-4429 Project: Kafka Issue Type: Improvem

[jira] [Created] (KAFKA-4442) Controller should grab lock when it is being initialized to avoid race condition

Dong Lin created KAFKA-4442: --- Summary: Controller should grab lock when it is being initialized to avoid race condition Key: KAFKA-4442 URL: https://issues.apache.org/jira/browse/KAFKA-4442 Project: Kafka

[jira] [Created] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

Dong Lin created KAFKA-4443: --- Summary: Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover Key: KAFKA-4443 URL: https://issues.apache.org/jira/browse/KAFKA-4443 Project

[jira] [Created] (KAFKA-4444) Aggregate requests sent from controller to broker during controlled shutdown

Dong Lin created KAFKA-: --- Summary: Aggregate requests sent from controller to broker during controlled shutdown Key: KAFKA- URL: https://issues.apache.org/jira/browse/KAFKA- Project: Kafka

[jira] [Created] (KAFKA-4445) PreferredLeaderElectionCommand should query zk only once per topic

Dong Lin created KAFKA-4445: --- Summary: PreferredLeaderElectionCommand should query zk only once per topic Key: KAFKA-4445 URL: https://issues.apache.org/jira/browse/KAFKA-4445 Project: Kafka Issue

[jira] [Updated] (KAFKA-4442) Controller should grab lock when it is being initialized to avoid race condition

[ https://issues.apache.org/jira/browse/KAFKA-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4442: Description: Currently controller will register broker change listener before sending send LeaderAndIsrRequ

[jira] [Updated] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4443: Description: Currently in onControllerFailover(), controller will startup replicaStatemachine and partition

[jira] [Commented] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707330#comment-15707330 ] Dong Lin commented on KAFKA-4443: - [~junrao] Sure. I just updated the description to corre

[jira] [Comment Edited] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707330#comment-15707330 ] Dong Lin edited comment on KAFKA-4443 at 11/30/16 2:55 AM: --- [~ju

[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&focusedCommentId=15707407#comment-15707407 ] Dong Lin commented on KAFKA-3042: - We recently made a fix in Kafka that may have the addre

[jira] [Resolved] (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:all-tabpanel ] Dong Lin resolved KAFKA-3042. - Resolution: Duplicate Assignee: Dong Lin The problem may have been solved in KAFKA-4443. > updateIs

[jira] [Updated] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

[ https://issues.apache.org/jira/browse/KAFKA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4415: Description: As of current implementation, when controller receives ControlledShutdownRequest, it will 1) f

[jira] [Commented] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

[ https://issues.apache.org/jira/browse/KAFKA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709345#comment-15709345 ] Dong Lin commented on KAFKA-4415: - [~ijuma] As of current Kafka implementation, Kafka does

[jira] [Created] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

Dong Lin created KAFKA-4485: --- Summary: Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader Key: KAFKA-4485 URL: https://issues.apache.org/jira/browse/KAFKA-4485 Pr

[jira] [Updated] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4485: Description: As of current implementation, we will exclude follower from ISR if the begin offset of FetchRe

[jira] [Updated] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4485: Description: As of current implementation, we will exclude follower from ISR if the begin offset of FetchRe

[jira] [Resolved] (KAFKA-4442) Controller should grab lock when it is being initialized to avoid race condition

[ https://issues.apache.org/jira/browse/KAFKA-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-4442. - Resolution: Invalid This patch is not needed because controller already has the lock when it is executing

[jira] [Updated] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4485: Description: As of current implementation, we will exclude follower from ISR if the begin offset of FetchRe

[jira] [Updated] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4485: Description: As of current implementation, we will exclude follower from ISR if the begin offset of FetchRe

[jira] [Created] (KAFKA-4521) MirrorMaker should flush all messages before releasing partition ownership during rebalance

Dong Lin created KAFKA-4521: --- Summary: MirrorMaker should flush all messages before releasing partition ownership during rebalance Key: KAFKA-4521 URL: https://issues.apache.org/jira/browse/KAFKA-4521 Proje

[jira] [Updated] (KAFKA-4521) MirrorMaker should flush all messages before releasing partition ownership during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4521: Description: In order to ensure that messages from a given partition in the source cluster are mirrored to

[jira] [Resolved] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-2442. - Resolution: Won't Fix > QuotasTest should not fail when cpu is busy >

[jira] [Commented] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767765#comment-15767765 ] Dong Lin commented on KAFKA-2442: - [~guozhang] I lost track of this issue and I am not sur

[jira] [Commented] (KAFKA-4429) records-lag should be zero if FetchResponse is empty

[ https://issues.apache.org/jira/browse/KAFKA-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15791770#comment-15791770 ] Dong Lin commented on KAFKA-4429: - [~kevinconaway] Receiving an empty FetchReponse is diff

[jira] [Created] (KAFKA-4586) Add purgeDataBefore() API in AdminClient

Dong Lin created KAFKA-4586: --- Summary: Add purgeDataBefore() API in AdminClient Key: KAFKA-4586 URL: https://issues.apache.org/jira/browse/KAFKA-4586 Project: Kafka Issue Type: New Feature

[jira] [Updated] (KAFKA-4586) Add purgeDataBefore() API in AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4586: Description: Please visit https://cwiki.apache.org/confluence/display/KAFKA/KIP-107%3A+Add+purgeDataBefore%2

[jira] [Created] (KAFKA-4820) ConsumerNetworkClient.send() should not require global lock

Dong Lin created KAFKA-4820: --- Summary: ConsumerNetworkClient.send() should not require global lock Key: KAFKA-4820 URL: https://issues.apache.org/jira/browse/KAFKA-4820 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-4820) ConsumerNetworkClient.send() should not require global lock

[ https://issues.apache.org/jira/browse/KAFKA-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4820: Description: Currently `ConsumerNetworkClient.send()` needs to acquire global lock of `ConumserNetworkClien

<    1   2   3   4   5   6   >