[jira] [Resolved] (KAFKA-10889) The log cleaner is not working for topic partitions

[ https://issues.apache.org/jira/browse/KAFKA-10889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-10889. -- Resolution: Not A Bug I am closing the issue as not a bug because the brokers were working

[jira] [Resolved] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

[ https://issues.apache.org/jira/browse/KAFKA-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-6029. - Resolution: Fixed > Controller should wait for the leader migration to finish before

[jira] [Created] (KAFKA-6568) LogCleanerManager.doneDeleting() should check the partition state before deleting the in progress partition

Jiangjie Qin created KAFKA-6568: --- Summary: LogCleanerManager.doneDeleting() should check the partition state before deleting the in progress partition Key: KAFKA-6568 URL: https://issues.apache.org/jira/browse

[jira] [Resolved] (KAFKA-6489) Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata refresh topics set.

[ https://issues.apache.org/jira/browse/KAFKA-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-6489. - Resolution: Fixed > Fetcher.retrieveOffsetsByTimes() should add all the topics to the metad

[jira] [Created] (KAFKA-6492) LogSemgent.truncateTo() should always resize the index file

Jiangjie Qin created KAFKA-6492: --- Summary: LogSemgent.truncateTo() should always resize the index file Key: KAFKA-6492 URL: https://issues.apache.org/jira/browse/KAFKA-6492 Project: Kafka

[jira] [Created] (KAFKA-6489) Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata refresh topics set.

Jiangjie Qin created KAFKA-6489: --- Summary: Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata refresh topics set. Key: KAFKA-6489 URL: https://issues.apache.org/jira/browse/KAFKA-6489

[jira] [Created] (KAFKA-6321) ConsumerGroupCommand should use the new consumer to query the log end offsets.

Jiangjie Qin created KAFKA-6321: --- Summary: ConsumerGroupCommand should use the new consumer to query the log end offsets. Key: KAFKA-6321 URL: https://issues.apache.org/jira/browse/KAFKA-6321 Project

[jira] [Created] (KAFKA-6304) The controller should allow update the partition reassignment for the partitions being reassigned

Jiangjie Qin created KAFKA-6304: --- Summary: The controller should allow update the partition reassignment for the partitions being reassigned Key: KAFKA-6304 URL: https://issues.apache.org/jira/browse/KAFKA-6304

[jira] [Created] (KAFKA-6264) Log cleaner thread may die on legacy segment containing messages whose offsets are too large

Jiangjie Qin created KAFKA-6264: --- Summary: Log cleaner thread may die on legacy segment containing messages whose offsets are too large Key: KAFKA-6264 URL: https://issues.apache.org/jira/browse/KAFKA-6264

[jira] [Resolved] (KAFKA-6157) Fix repeated words words in JavaDoc and comments.

[ https://issues.apache.org/jira/browse/KAFKA-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-6157. - Resolution: Fixed > Fix repeated words words in JavaDoc and comme

[jira] [Created] (KAFKA-6083) The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found.

Jiangjie Qin created KAFKA-6083: --- Summary: The Fetcher should add the InvalidRecordException as a cause to the KafkaException when invalid record is found. Key: KAFKA-6083 URL: https://issues.apache.org/jira/browse

[jira] [Created] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

Jiangjie Qin created KAFKA-6029: --- Summary: Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest Key: KAFKA-6029 URL: https://issues.apache.org/jira/browse/KAFKA-6029

[jira] [Created] (KAFKA-6028) Improve the quota throttle communication.

Jiangjie Qin created KAFKA-6028: --- Summary: Improve the quota throttle communication. Key: KAFKA-6028 URL: https://issues.apache.org/jira/browse/KAFKA-6028 Project: Kafka Issue Type

[jira] [Created] (KAFKA-5834) AbstractConfig.logUnused() may log confusing warning information.

Jiangjie Qin created KAFKA-5834: --- Summary: AbstractConfig.logUnused() may log confusing warning information. Key: KAFKA-5834 URL: https://issues.apache.org/jira/browse/KAFKA-5834 Project: Kafka

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

[ https://issues.apache.org/jira/browse/KAFKA-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-5694. - Resolution: Implemented Fix Version/s: 1.0.0 > Add ChangeReplicaDirRequ

[jira] [Created] (KAFKA-5782) Avoid unnecessary PID reset when expire batches.

Jiangjie Qin created KAFKA-5782: --- Summary: Avoid unnecessary PID reset when expire batches. Key: KAFKA-5782 URL: https://issues.apache.org/jira/browse/KAFKA-5782 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-5681) jarAll does not build all scala versions anymore.

[ https://issues.apache.org/jira/browse/KAFKA-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-5681. - Resolution: Won't Fix Discussed in the PR. Closing the ticket as won't fix. > jarAll d

[jira] [Created] (KAFKA-5681) jarAll does not build all scala versions anymore.

Jiangjie Qin created KAFKA-5681: --- Summary: jarAll does not build all scala versions anymore. Key: KAFKA-5681 URL: https://issues.apache.org/jira/browse/KAFKA-5681 Project: Kafka Issue Type

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

[ https://issues.apache.org/jira/browse/KAFKA-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-5627. - Resolution: Fixed > Reduce classes needed for LeaderAndIsrPartitionSt

[jira] [Commented] (KAFKA-5453) Controller may miss requests sent to the broker when zk session timeout happens.

[ https://issues.apache.org/jira/browse/KAFKA-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050070#comment-16050070 ] Jiangjie Qin commented on KAFKA-5453: - I don't think so. This is a probably a bug since some pretty

[jira] [Created] (KAFKA-5453) Controller may miss requests sent to the broker when zk session timeout happens.

Jiangjie Qin created KAFKA-5453: --- Summary: Controller may miss requests sent to the broker when zk session timeout happens. Key: KAFKA-5453 URL: https://issues.apache.org/jira/browse/KAFKA-5453 Project

[jira] [Updated] (KAFKA-5453) Controller may miss requests sent to the broker when zk session timeout happens.

[ https://issues.apache.org/jira/browse/KAFKA-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5453: Affects Version/s: 0.11.0.0 > Controller may miss requests sent to the broker when zk sess

[jira] [Updated] (KAFKA-5453) Controller may miss requests sent to the broker when zk session timeout happens.

[ https://issues.apache.org/jira/browse/KAFKA-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5453: Component/s: core > Controller may miss requests sent to the broker when zk session time

[jira] [Updated] (KAFKA-5453) Controller may miss requests sent to the broker when zk session timeout happens.

[ https://issues.apache.org/jira/browse/KAFKA-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5453: Fix Version/s: 0.11.1.0 > Controller may miss requests sent to the broker when zk session time

[jira] [Updated] (KAFKA-5344) Change message.timestamp.difference.max.ms back to Long.MaxValue

[ https://issues.apache.org/jira/browse/KAFKA-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5344: Status: Patch Available (was: Open) > Change message.timestamp.difference.max.ms b

[jira] [Created] (KAFKA-5344) Change message.timestamp.difference.max.ms back to Long.MaxValue

Jiangjie Qin created KAFKA-5344: --- Summary: Change message.timestamp.difference.max.ms back to Long.MaxValue Key: KAFKA-5344 URL: https://issues.apache.org/jira/browse/KAFKA-5344 Project: Kafka

[jira] [Resolved] (KAFKA-5078) PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

[ https://issues.apache.org/jira/browse/KAFKA-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-5078. - Resolution: Fixed > PartitionRecords.fetchRecords(...) should defer exception to the next c

[jira] [Updated] (KAFKA-5078) PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

[ https://issues.apache.org/jira/browse/KAFKA-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5078: Fix Version/s: 0.11.0.0 > PartitionRecords.fetchRecords(...) should defer exception to the n

[jira] [Commented] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026532#comment-16026532 ] Jiangjie Qin commented on KAFKA-5329: - [~ijuma] The ControllerContext is fine. This ticket

[jira] [Updated] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5329: Summary: Replica list in the metadata cache on the broker may have different order from zookeeper

[jira] [Created] (KAFKA-5329) Metadata cache on the broker may have replica list may have different order from zookeeper

Jiangjie Qin created KAFKA-5329: --- Summary: Metadata cache on the broker may have replica list may have different order from zookeeper Key: KAFKA-5329 URL: https://issues.apache.org/jira/browse/KAFKA-5329

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023641#comment-16023641 ] Jiangjie Qin commented on KAFKA-5211: - [~enothereska] I think a KIP is only required

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023619#comment-16023619 ] Jiangjie Qin commented on KAFKA-4340: - [~edenhill] I think one of the well established guarantee

[jira] [Updated] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5211: Status: Patch Available (was: In Progress) > KafkaConsumer should not skip a corrupted rec

[jira] [Updated] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Resolution: Fixed Status: Resolved (was: Patch Available) > Split the ProducerBa

[jira] [Updated] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Fix Version/s: 0.11.0.0 > Split the ProducerBatch and resend when received RecordTooLargeExcept

[jira] [Work started] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5211 started by Jiangjie Qin. --- > KafkaConsumer should not skip a corrupted record after throwing an except

[jira] [Commented] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008634#comment-16008634 ] Jiangjie Qin commented on KAFKA-3995: - [~ijuma] done. > Split the ProducerBatch and resend w

[jira] [Updated] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5211: Fix Version/s: 0.11.0.0 > KafkaConsumer should not skip a corrupted record after throw

[jira] [Updated] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Summary: Split the ProducerBatch and resend when received RecordTooLargeException (was: Add a new

[jira] [Created] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

Jiangjie Qin created KAFKA-5211: --- Summary: KafkaConsumer should not skip a corrupted record after throwing an exception. Key: KAFKA-5211 URL: https://issues.apache.org/jira/browse/KAFKA-5211 Project

[jira] [Commented] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001780#comment-16001780 ] Jiangjie Qin commented on KAFKA-3554: - [~airbots] I lose track of this ticket... It was not checked

[jira] [Commented] (KAFKA-5075) Defer exception to the next pollOnce() if consumer's fetch position has already increased

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971892#comment-15971892 ] Jiangjie Qin commented on KAFKA-5075: - [~hachikuji] [~gwenshap] I've cherry-picked the patch to 0.10.2

[jira] [Commented] (KAFKA-5075) Defer exception to the next pollOnce() if consumer's fetch position has already increased

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971639#comment-15971639 ] Jiangjie Qin commented on KAFKA-5075: - [~hachikuji] I also think it is worth fixing. [~gwenshap] I'll

[jira] [Commented] (KAFKA-5075) Defer exception to the next pollOnce() if consumer's fetch position has already increased

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970771#comment-15970771 ] Jiangjie Qin commented on KAFKA-5075: - [~gwenshap] The patch has been checked in. Thanks

[jira] [Commented] (KAFKA-5075) The position in the consumers may be advanced incorrectly when some exception is thrown from consumer.poll()

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969730#comment-15969730 ] Jiangjie Qin commented on KAFKA-5075: - [~lindong] is currently working on the patch. Hopefully we can

[jira] [Commented] (KAFKA-5075) The position in the consumers may be advanced incorrectly when some exception is thrown from consumer.poll()

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969699#comment-15969699 ] Jiangjie Qin commented on KAFKA-5075: - [~gwenshap] I was actually about to reply on the 0.10.2.1-RC1

[jira] [Assigned] (KAFKA-5075) The position in the consumers may be advanced incorrectly when some exception is thrown from consumer.poll()

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-5075: --- Assignee: Dong Lin > The position in the consumers may be advanced incorrectly when s

[jira] [Updated] (KAFKA-5075) The position in the consumers may be advanced incorrectly when some exception is thrown from consumer.poll()

[ https://issues.apache.org/jira/browse/KAFKA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5075: Affects Version/s: 0.10.2.0 Fix Version/s: 0.10.2.1 Component/s: consumer

[jira] [Created] (KAFKA-5075) The position in the consumers may be advanced incorrectly when some exception is thrown from consumer.poll()

Jiangjie Qin created KAFKA-5075: --- Summary: The position in the consumers may be advanced incorrectly when some exception is thrown from consumer.poll() Key: KAFKA-5075 URL: https://issues.apache.org/jira/browse

[jira] [Resolved] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4401. - Resolution: Fixed > Change the KafkaServerTestHarness and IntegrationTestHarness from tr

[jira] [Commented] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961463#comment-15961463 ] Jiangjie Qin commented on KAFKA-4401: - Sure, I just linked KAFKA-5041 to this ticket so we can see

[jira] [Assigned] (KAFKA-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-5011: --- Assignee: Jiangjie Qin > Replica fetchers may need to down-convert messages dur

[jira] [Commented] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927460#comment-15927460 ] Jiangjie Qin commented on KAFKA-4907: - I see. Yeah, the default behavior probably should just

[jira] [Assigned] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-4907: --- Assignee: Jiangjie Qin > compacted topic shouldn't reject messages with old timest

[jira] [Commented] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927438#comment-15927438 ] Jiangjie Qin commented on KAFKA-4907: - [~ijuma] Hmm, if {{cleanup.policy}} is NOT set to {{delete

[jira] [Commented] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927392#comment-15927392 ] Jiangjie Qin commented on KAFKA-4907: - [~junrao] Thanks for the explanation. Yes, that does sound

[jira] [Commented] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927231#comment-15927231 ] Jiangjie Qin commented on KAFKA-4907: - [~junrao] Are you referring to the log cleaner? The log cleaner

[jira] [Resolved] (KAFKA-4891) kafka.request.logger TRACE regression

[ https://issues.apache.org/jira/browse/KAFKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4891. - Resolution: Fixed > kafka.request.logger TRACE regress

[jira] [Updated] (KAFKA-4891) kafka.request.logger TRACE regression

[ https://issues.apache.org/jira/browse/KAFKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4891: Fix Version/s: (was: 0.10.2.1) 0.11.0.0 > kafka.request.logger TR

[jira] [Updated] (KAFKA-4891) kafka.request.logger TRACE regression

[ https://issues.apache.org/jira/browse/KAFKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4891: Fix Version/s: 0.10.2.1 > kafka.request.logger TRACE regress

[jira] [Commented] (KAFKA-4877) Expose TimestampType in Producer RecordMetadata

[ https://issues.apache.org/jira/browse/KAFKA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904148#comment-15904148 ] Jiangjie Qin commented on KAFKA-4877: - [~hachikuji] The original idea was that the producer should

[jira] [Resolved] (KAFKA-4833) Transient unit test failure in AbstractCoordinatorTest

[ https://issues.apache.org/jira/browse/KAFKA-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4833. - Resolution: Invalid Just noticed that the test was failing on a review branch instead of trunk

[jira] [Updated] (KAFKA-4833) Transient unit test failure in AbstractCoordinatorTest

[ https://issues.apache.org/jira/browse/KAFKA-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4833: Affects Version/s: 0.10.2.0 > Transient unit test failure in AbstractCoordinatorT

[jira] [Updated] (KAFKA-4833) Transient unit test failure in AbstractCoordinatorTest

[ https://issues.apache.org/jira/browse/KAFKA-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4833: Description: I saw this couple of times when running unit test locally. Haven't looked

[jira] [Created] (KAFKA-4833) Transient unit test failure in AbstractCoordinatorTest

Jiangjie Qin created KAFKA-4833: --- Summary: Transient unit test failure in AbstractCoordinatorTest Key: KAFKA-4833 URL: https://issues.apache.org/jira/browse/KAFKA-4833 Project: Kafka Issue

[jira] [Commented] (KAFKA-3436) Speed up controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884419#comment-15884419 ] Jiangjie Qin commented on KAFKA-3436: - Sorry you are right. I was under the impression that patch

[jira] [Commented] (KAFKA-3436) Speed up controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884390#comment-15884390 ] Jiangjie Qin commented on KAFKA-3436: - [~onurkaraman] is currently working on rewrite controller

[jira] [Updated] (KAFKA-3995) Add a new configuration "enable.compression.ratio.estimation" to the producer config

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Summary: Add a new configuration "enable.compression.ratio.estimation" to the produ

[jira] [Resolved] (KAFKA-4757) Improve NetworkClient trace logging of request details

[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4757. - Resolution: Fixed > Improve NetworkClient trace logging of request deta

[jira] [Updated] (KAFKA-4757) Improve NetworkClient trace logging of request details

[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4757: Affects Version/s: 0.10.2.0 > Improve NetworkClient trace logging of request deta

[jira] [Updated] (KAFKA-4757) Improve NetworkClient trace logging of request details

[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4757: Fix Version/s: 0.10.3.0 > Improve NetworkClient trace logging of request deta

[jira] [Updated] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4340: Resolution: Fixed Status: Resolved (was: Patch Available) > Change the default va

[jira] [Comment Edited] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868777#comment-15868777 ] Jiangjie Qin edited comment on KAFKA-4340 at 2/15/17 11:05 PM: --- [~junrao

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868777#comment-15868777 ] Jiangjie Qin commented on KAFKA-4340: - [~junrao] [~ijuma] [~cmccabe] I created https://github.com

[jira] [Resolved] (KAFKA-4735) Fix deadlock issue during MM shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4735. - Resolution: Fixed > Fix deadlock issue during MM shutd

[jira] [Updated] (KAFKA-4735) Fix deadlock issue during MM shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4735: Affects Version/s: 0.10.2.0 Fix Version/s: 0.10.3.0 > Fix deadlock issue during MM shutd

[jira] [Commented] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825006#comment-15825006 ] Jiangjie Qin commented on KAFKA-4401: - [~ewencp] I think it is a good suggestion. Technically speaking

[jira] [Commented] (KAFKA-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823583#comment-15823583 ] Jiangjie Qin commented on KAFKA-3190: - [~ewencp] This remains an issue and confuses some

[jira] [Commented] (KAFKA-4381) Add per partition lag metric to KafkaConsumer.

[ https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15805168#comment-15805168 ] Jiangjie Qin commented on KAFKA-4381: - [~ijuma] Thanks for the reminder :) I'll submit patch

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15805165#comment-15805165 ] Jiangjie Qin commented on KAFKA-4497: - [~michael.andre.pearce] Thanks for the update. Glad to know

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15800696#comment-15800696 ] Jiangjie Qin commented on KAFKA-4497: - [~michael.andre.pearce] Thanks for helping test this again. I

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15800498#comment-15800498 ] Jiangjie Qin commented on KAFKA-4497: - [~michael.andre.pearce] Sorry for the late response, just got

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786213#comment-15786213 ] Jiangjie Qin commented on KAFKA-4497: - [~sandieg] I cannot think of a good workaround on this without

[jira] [Updated] (KAFKA-2980) ZookeeperConsumerConnector may enter deadlock if a rebalance occurs during a stream creation.

[ https://issues.apache.org/jira/browse/KAFKA-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2980: Resolution: Cannot Reproduce Status: Resolved (was: Patch Available

[jira] [Updated] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4447: Fix Version/s: 0.10.2.0 > Controller resigned but it also acts as a controller for a long t

[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 ] Jiangjie Qin updated KAFKA-4521: Affects Version/s: 0.10.1.0 Fix Version/s: 0.10.2.0 > MirrorMaker should flush all messa

[jira] [Resolved] (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 ] Jiangjie Qin resolved KAFKA-4521. - Resolution: Fixed > MirrorMaker should flush all messages before releasing partition owners

[jira] [Work started] (KAFKA-4529) tombstone may be removed earlier than it should

[ https://issues.apache.org/jira/browse/KAFKA-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4529 started by Jiangjie Qin. --- > tombstone may be removed earlier than it sho

[jira] [Assigned] (KAFKA-4529) tombstone may be removed earlier than it should

[ https://issues.apache.org/jira/browse/KAFKA-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-4529: --- Assignee: Jiangjie Qin > tombstone may be removed earlier than it sho

[jira] [Commented] (KAFKA-4529) tombstone may be removed earlier than it should

[ https://issues.apache.org/jira/browse/KAFKA-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744529#comment-15744529 ] Jiangjie Qin commented on KAFKA-4529: - Sure, I'll submit a patch. > tombstone may be removed earl

[jira] [Comment Edited] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743650#comment-15743650 ] Jiangjie Qin edited comment on KAFKA-4497 at 12/13/16 12:40 AM: The bit

[jira] [Comment Edited] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743650#comment-15743650 ] Jiangjie Qin edited comment on KAFKA-4497 at 12/13/16 12:38 AM

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743650#comment-15743650 ] Jiangjie Qin commented on KAFKA-4497: - The negative bit is the MSB which is 1 in 0X. The entry

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743122#comment-15743122 ] Jiangjie Qin commented on KAFKA-4497: - [~junrao] I think 0x is actually -1, right? In the time

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15739035#comment-15739035 ] Jiangjie Qin commented on KAFKA-4497: - To be more clear, this part of the code has been changed

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15739018#comment-15739018 ] Jiangjie Qin commented on KAFKA-4497: - I looked at the log cleaner code in 0.10.1. There is a bug

[jira] [Assigned] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-4497: --- Assignee: Jiangjie Qin > log cleaner breaks on timein

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

[ https://issues.apache.org/jira/browse/KAFKA-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4445. - Resolution: Fixed > PreferredLeaderElectionCommand should query zk only once per to

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

[ https://issues.apache.org/jira/browse/KAFKA-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4445: Affects Version/s: 0.10.1.0 Fix Version/s: 0.10.2.0 Issue Type: Improvement

  1   2   3   4   5   6   7   8   9   10   >