[jira] [Commented] (KAFKA-10017) Flaky Test EosBetaUpgradeIntegrationTest.shouldUpgradeFromEosAlphaToEosBeta

[ https://issues.apache.org/jira/browse/KAFKA-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152329#comment-17152329 ] Guozhang Wang commented on KAFKA-10017: --- Hi [~rhauch] I've just pushed a PR from [~ableegoldman]

[jira] [Updated] (KAFKA-806) Index may not always observe log.index.interval.bytes

[ https://issues.apache.org/jira/browse/KAFKA-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-806: Labels: newbie++ (was: ) > Index may not always observe log.index.interval.bytes >

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151465#comment-17151465 ] Guozhang Wang commented on KAFKA-10134: --- [~seanguo] thanks for confirming! As the root cause is

[jira] [Commented] (KAFKA-10229) Kafka stream dies for no apparent reason, no errors logged on client or server

[ https://issues.apache.org/jira/browse/KAFKA-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151448#comment-17151448 ] Guozhang Wang commented on KAFKA-10229: --- Hello [~rocketraman] thanks for reporting this. From your

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149122#comment-17149122 ] Guozhang Wang commented on KAFKA-10134: --- I've updated the PR. > High CPU issue during rebalance

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148854#comment-17148854 ] Guozhang Wang commented on KAFKA-10134: --- [~neowu0] Thanks for your comments. I will incorporate

[jira] [Updated] (KAFKA-10017) Flaky Test EosBetaUpgradeIntegrationTest.shouldUpgradeFromEosAlphaToEosBeta

[ https://issues.apache.org/jira/browse/KAFKA-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10017: -- Priority: Blocker (was: Critical) > Flaky Test

[jira] [Commented] (KAFKA-10017) Flaky Test EosBetaUpgradeIntegrationTest.shouldUpgradeFromEosAlphaToEosBeta

[ https://issues.apache.org/jira/browse/KAFKA-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148846#comment-17148846 ] Guozhang Wang commented on KAFKA-10017: --- [~rhauch] I'm making it back as a blocker for 2.6 since

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148261#comment-17148261 ] Guozhang Wang commented on KAFKA-10134: --- Hey [~neowu0] thanks a lot for your comments. Much

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148190#comment-17148190 ] Guozhang Wang commented on KAFKA-10134: --- Here's my reasoning: if there are still some owned

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148183#comment-17148183 ] Guozhang Wang commented on KAFKA-10134: --- [~neowu0] What's still puzzling me is that, even in the

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146706#comment-17146706 ] Guozhang Wang commented on KAFKA-10134: --- I've provided a PR for trunk, but it should apply cleanly

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146678#comment-17146678 ] Guozhang Wang commented on KAFKA-10134: --- [~seanguo] I think [~neowu0]'s brought up issue is a

[jira] [Assigned] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-10134: - Assignee: Guozhang Wang > High CPU issue during rebalance in Kafka consumer after

[jira] [Created] (KAFKA-10199) Separate state restoration into separate threads

Guozhang Wang created KAFKA-10199: - Summary: Separate state restoration into separate threads Key: KAFKA-10199 URL: https://issues.apache.org/jira/browse/KAFKA-10199 Project: Kafka Issue

[jira] [Commented] (KAFKA-10186) Aborting transaction with pending data should throw non-fatal exception

[ https://issues.apache.org/jira/browse/KAFKA-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141531#comment-17141531 ] Guozhang Wang commented on KAFKA-10186: --- Also cc [~hachikuji] [~bob-barrett] > Aborting

[jira] [Updated] (KAFKA-10173) BufferUnderflowException during Kafka Streams Upgrade

[ https://issues.apache.org/jira/browse/KAFKA-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10173: -- Labels: suppress (was: ) > BufferUnderflowException during Kafka Streams Upgrade >

[jira] [Commented] (KAFKA-10121) Streams Task Assignment optimization design

[ https://issues.apache.org/jira/browse/KAFKA-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141289#comment-17141289 ] Guozhang Wang commented on KAFKA-10121: --- Thanks for filing this ticket John! Since this is a more

[jira] [Commented] (KAFKA-9995) IllegalStateException when offsets not found

[ https://issues.apache.org/jira/browse/KAFKA-9995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140763#comment-17140763 ] Guozhang Wang commented on KAFKA-9995: -- Hello James, sorry for the late reply. Your observed issue

[jira] [Resolved] (KAFKA-10167) Streams EOS-Beta should not try to get end-offsets as read-committed

[ https://issues.apache.org/jira/browse/KAFKA-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10167. --- Resolution: Fixed > Streams EOS-Beta should not try to get end-offsets as read-committed >

[jira] [Comment Edited] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139533#comment-17139533 ] Guozhang Wang edited comment on KAFKA-10005 at 6/18/20, 6:58 PM: - So

[jira] [Commented] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139919#comment-17139919 ] Guozhang Wang commented on KAFKA-10005: --- I think even if we only move standbys to separate

[jira] [Updated] (KAFKA-10184) Flaky HighAvailabilityTaskAssignorIntegrationTest.shouldScaleOutWithWarmupTasksAndPersistentStores

[ https://issues.apache.org/jira/browse/KAFKA-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10184: -- Issue Type: Test (was: Bug) > Flaky >

[jira] [Updated] (KAFKA-10184) Flaky HighAvailabilityTaskAssignorIntegrationTest.shouldScaleOutWithWarmupTasksAndPersistentStores

[ https://issues.apache.org/jira/browse/KAFKA-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10184: -- Priority: Minor (was: Major) > Flaky >

[jira] [Created] (KAFKA-10184) Flaky HighAvailabilityTaskAssignorIntegrationTest.shouldScaleOutWithWarmupTasksAndPersistentStores

Guozhang Wang created KAFKA-10184: - Summary: Flaky HighAvailabilityTaskAssignorIntegrationTest.shouldScaleOutWithWarmupTasksAndPersistentStores Key: KAFKA-10184 URL:

[jira] [Commented] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139533#comment-17139533 ] Guozhang Wang commented on KAFKA-10005: --- So just to have a quick summary, my proposal is primarily

[jira] [Commented] (KAFKA-10091) Improve task idling

[ https://issues.apache.org/jira/browse/KAFKA-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138832#comment-17138832 ] Guozhang Wang commented on KAFKA-10091: --- We had a quick offline sync about the known scenarios

[jira] [Commented] (KAFKA-10167) Streams EOS-Beta should not try to get end-offsets as read-committed

[ https://issues.apache.org/jira/browse/KAFKA-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136216#comment-17136216 ] Guozhang Wang commented on KAFKA-10167: --- I've also thought about whether we need to block on

[jira] [Commented] (KAFKA-10167) Streams EOS-Beta should not try to get end-offsets as read-committed

[ https://issues.apache.org/jira/browse/KAFKA-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136215#comment-17136215 ] Guozhang Wang commented on KAFKA-10167: --- The proposed solution is that even under EOS, do not try

[jira] [Created] (KAFKA-10167) Streams EOS-Beta should not try to get end-offsets as read-committed

Guozhang Wang created KAFKA-10167: - Summary: Streams EOS-Beta should not try to get end-offsets as read-committed Key: KAFKA-10167 URL: https://issues.apache.org/jira/browse/KAFKA-10167 Project:

[jira] [Commented] (KAFKA-10134) High CPU issue during rebalance in Kafka consumer after upgrading to 2.5

[ https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136069#comment-17136069 ] Guozhang Wang commented on KAFKA-10134: --- This is a bit weird to me -- discover of coordinator

[jira] [Assigned] (KAFKA-9450) Decouple inner state flushing from committing

[ https://issues.apache.org/jira/browse/KAFKA-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-9450: Assignee: Guozhang Wang > Decouple inner state flushing from committing >

[jira] [Resolved] (KAFKA-9991) Flaky Test KTableSourceTopicRestartIntegrationTest.shouldRestoreAndProgressWhenTopicWrittenToDuringRestorationWithEosAlphaEnabled

[ https://issues.apache.org/jira/browse/KAFKA-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9991. -- Fix Version/s: 2.6.0 Resolution: Fixed > Flaky Test >

[jira] [Resolved] (KAFKA-9182) Flaky Test org.apache.kafka.streams.integration.KTableSourceTopicRestartIntegrationTest.shouldRestoreAndProgressWhenTopicWrittenToDuringRestorationWithEosEnabled

[ https://issues.apache.org/jira/browse/KAFKA-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9182. -- Fix Version/s: 2.6.0 Resolution: Fixed Resolved as part of

[jira] [Created] (KAFKA-10122) Consumer should allow heartbeat during rebalance as well

Guozhang Wang created KAFKA-10122: - Summary: Consumer should allow heartbeat during rebalance as well Key: KAFKA-10122 URL: https://issues.apache.org/jira/browse/KAFKA-10122 Project: Kafka

[jira] [Resolved] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10005. --- Fix Version/s: 2.6.0 Assignee: Guozhang Wang Resolution: Fixed > Decouple

[jira] [Resolved] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8803. -- Resolution: Fixed > Stream will not start due to TimeoutException: Timeout expired after >

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128662#comment-17128662 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Have you seen it again since then? > Stream

[jira] [Commented] (KAFKA-10091) Improve task idling

[ https://issues.apache.org/jira/browse/KAFKA-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127720#comment-17127720 ] Guozhang Wang commented on KAFKA-10091: --- Thanks John. I think you're concerning about some issues

[jira] [Commented] (KAFKA-6435) Application Reset Tool might delete incorrect internal topics

[ https://issues.apache.org/jira/browse/KAFKA-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127715#comment-17127715 ] Guozhang Wang commented on KAFKA-6435: -- What about just adding a `--internal-topics` instead of a

[jira] [Commented] (KAFKA-10091) Improve task idling

[ https://issues.apache.org/jira/browse/KAFKA-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125546#comment-17125546 ] Guozhang Wang commented on KAFKA-10091: --- Hi John, not sure I understand the last statement `that

[jira] [Commented] (KAFKA-6502) Kafka streams deserialization handler not committing offsets on error records

[ https://issues.apache.org/jira/browse/KAFKA-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121269#comment-17121269 ] Guozhang Wang commented on KAFKA-6502: -- I think it is not fixed via KAFKA-6607 since if the

[jira] [Resolved] (KAFKA-9561) Update task input partitions when topic metadata changes

[ https://issues.apache.org/jira/browse/KAFKA-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9561. -- Resolution: Fixed > Update task input partitions when topic metadata changes >

[jira] [Resolved] (KAFKA-9898) Flaky Test StoreQueryIntegrationTest.shouldQueryAllStalePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9898. -- Fix Version/s: 2.6.0 Resolution: Fixed > Flaky Test

[jira] [Assigned] (KAFKA-9898) Flaky Test StoreQueryIntegrationTest.shouldQueryAllStalePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-9898: Assignee: Guozhang Wang > Flaky Test

[jira] [Commented] (KAFKA-9898) Flaky Test StoreQueryIntegrationTest.shouldQueryAllStalePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116950#comment-17116950 ] Guozhang Wang commented on KAFKA-9898: -- I'd mark it as resolved by

[jira] [Commented] (KAFKA-9897) Flaky Test StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116948#comment-17116948 ] Guozhang Wang commented on KAFKA-9897: -- https://github.com/apache/kafka/pull/8568

[jira] [Resolved] (KAFKA-10022) console-producer supports the setting of client.id

[ https://issues.apache.org/jira/browse/KAFKA-10022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10022. --- Fix Version/s: 2.6.0 Resolution: Fixed > console-producer supports the setting of

[jira] [Commented] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114342#comment-17114342 ] Guozhang Wang commented on KAFKA-10005: --- Here's a rough idea to replace the bulk loading configs:

[jira] [Commented] (KAFKA-9168) Integrate JNI direct buffer support to RocksDBStore

[ https://issues.apache.org/jira/browse/KAFKA-9168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114291#comment-17114291 ] Guozhang Wang commented on KAFKA-9168: -- Just add a reference that this feature is only available in

[jira] [Assigned] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-10005: - Assignee: (was: Guozhang Wang) > Decouple RestoreListener from RestoreCallback and

[jira] [Resolved] (KAFKA-1056) Evenly Distribute Intervals in OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1056. -- Resolution: Fixed > Evenly Distribute Intervals in OffsetIndex >

[jira] [Commented] (KAFKA-8159) Built-in serdes for signed numbers do not obey lexicographical ordering

[ https://issues.apache.org/jira/browse/KAFKA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17112511#comment-17112511 ] Guozhang Wang commented on KAFKA-8159: -- Hey John, What I was asking is actually beyond signed

[jira] [Commented] (KAFKA-6579) Consolidate window store and session store unit tests into a single class

[ https://issues.apache.org/jira/browse/KAFKA-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17112447#comment-17112447 ] Guozhang Wang commented on KAFKA-6579: -- [~mikulskibartosz] please feel free to take a stab at it, I

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110447#comment-17110447 ] Guozhang Wang commented on KAFKA-6520: -- Just to throw some more ideas here: the embedded clients are

[jira] [Commented] (KAFKA-10010) Should close standby task for safety during HandleLostAll

[ https://issues.apache.org/jira/browse/KAFKA-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109604#comment-17109604 ] Guozhang Wang commented on KAFKA-10010: --- We intentionally did not close standby tasks because they

[jira] [Resolved] (KAFKA-9617) Replica Fetcher can mark partition as failed when max.message.bytes is changed

[ https://issues.apache.org/jira/browse/KAFKA-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9617. -- Fix Version/s: 2.6.0 Resolution: Fixed > Replica Fetcher can mark partition as failed

[jira] [Updated] (KAFKA-10001) Store's own restore listener should be triggered in store changelog reader

[ https://issues.apache.org/jira/browse/KAFKA-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10001: -- Labels: streams (was: ) > Store's own restore listener should be triggered in store

[jira] [Resolved] (KAFKA-10001) Store's own restore listener should be triggered in store changelog reader

[ https://issues.apache.org/jira/browse/KAFKA-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10001. --- Fix Version/s: 2.6.0 Resolution: Fixed > Store's own restore listener should be

[jira] [Resolved] (KAFKA-8918) Flaky Test org.apache.kafka.trogdor.coordinator.CoordinatorTest.testTaskCancellation

[ https://issues.apache.org/jira/browse/KAFKA-8918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8918. -- Resolution: Fixed > Flaky Test >

[jira] [Resolved] (KAFKA-8197) Flaky Test kafka.server.DynamicBrokerConfigTest > testPasswordConfigEncoderSecretChange

[ https://issues.apache.org/jira/browse/KAFKA-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8197. -- Resolution: Fixed > Flaky Test kafka.server.DynamicBrokerConfigTest > >

[jira] [Commented] (KAFKA-6579) Consolidate window store and session store unit tests into a single class

[ https://issues.apache.org/jira/browse/KAFKA-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109100#comment-17109100 ] Guozhang Wang commented on KAFKA-6579: -- [~ableegoldman] Is it resolved now? > Consolidate window

[jira] [Assigned] (KAFKA-5209) Transient failure: kafka.server.MetadataRequestTest.testControllerId

[ https://issues.apache.org/jira/browse/KAFKA-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5209: Assignee: (was: Umesh Chaudhary) > Transient failure:

[jira] [Resolved] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

[ https://issues.apache.org/jira/browse/KAFKA-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7042. -- Resolution: Not A Problem > Fall back to the old behavior when the broker is too old to

[jira] [Resolved] (KAFKA-5719) Create a quickstart archetype project for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5719. -- Resolution: Fixed > Create a quickstart archetype project for Kafka Streams >

[jira] [Updated] (KAFKA-2045) Memory Management on the consumer

[ https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2045: - Labels: newbie++ (was: ) > Memory Management on the consumer >

[jira] [Resolved] (KAFKA-3103) Transient Failure in kafka.integration.PlaintextTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

[ https://issues.apache.org/jira/browse/KAFKA-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3103. -- Resolution: Fixed > Transient Failure in >

[jira] [Resolved] (KAFKA-1985) Document on possible error codes for each response type

[ https://issues.apache.org/jira/browse/KAFKA-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1985. -- Resolution: Fixed > Document on possible error codes for each response type >

[jira] [Resolved] (KAFKA-1617) Move Metadata Cache to TopicManager and handling of Offset Request to LogManager

[ https://issues.apache.org/jira/browse/KAFKA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1617. -- Resolution: Won't Fix > Move Metadata Cache to TopicManager and handling of Offset Request to

[jira] [Resolved] (KAFKA-3168) Failure in kafka.integration.PrimitiveApiTest.testPipelinedProduceRequests

[ https://issues.apache.org/jira/browse/KAFKA-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3168. -- Resolution: Fixed > Failure in kafka.integration.PrimitiveApiTest.testPipelinedProduceRequests

[jira] [Assigned] (KAFKA-3168) Failure in kafka.integration.PrimitiveApiTest.testPipelinedProduceRequests

[ https://issues.apache.org/jira/browse/KAFKA-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-3168: Assignee: (was: Parag Shah) > Failure in

[jira] [Assigned] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-3261: Assignee: (was: chen zhu) > Consolidate class kafka.cluster.BrokerEndPoint and

[jira] [Updated] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3261: - Labels: newbie (was: ) > Consolidate class kafka.cluster.BrokerEndPoint and

[jira] [Resolved] (KAFKA-3738) Add load system tests for Streams

[ https://issues.apache.org/jira/browse/KAFKA-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3738. -- Resolution: Fixed We have soak tests and perf benchmarks today. > Add load system tests for

[jira] [Resolved] (KAFKA-3220) Failure in kafka.server.ClientQuotaManagerTest.testQuotaViolation

[ https://issues.apache.org/jira/browse/KAFKA-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3220. -- Resolution: Fixed Did not see this recently. > Failure in

[jira] [Resolved] (KAFKA-1602) Use single error code for offset commit response

[ https://issues.apache.org/jira/browse/KAFKA-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1602. -- Resolution: Not A Problem > Use single error code for offset commit response >

[jira] [Resolved] (KAFKA-4143) Transient failure in kafka.server.SaslSslReplicaFetchTest.testReplicaFetcherThread

[ https://issues.apache.org/jira/browse/KAFKA-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4143. -- Resolution: Fixed Did not see this recently. > Transient failure in >

[jira] [Comment Edited] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108682#comment-17108682 ] Guozhang Wang edited comment on KAFKA-10005 at 5/15/20, 9:41 PM: -

[jira] [Commented] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108682#comment-17108682 ] Guozhang Wang commented on KAFKA-10005: --- Relevant rockdb APIs to explore:

[jira] [Commented] (KAFKA-7041) Using RocksDB bulk loading for StandbyTasks

[ https://issues.apache.org/jira/browse/KAFKA-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108669#comment-17108669 ] Guozhang Wang commented on KAFKA-7041: -- I filed KAFKA-10005 for exploring the possibility if

[jira] [Updated] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10005: -- Description: In Kafka Streams we have two restoration callbacks: * RestoreCallback

[jira] [Created] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

Guozhang Wang created KAFKA-10005: - Summary: Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB Key: KAFKA-10005 URL: https://issues.apache.org/jira/browse/KAFKA-10005

[jira] [Resolved] (KAFKA-7174) Improve version probing of subscription info

[ https://issues.apache.org/jira/browse/KAFKA-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7174. -- Resolution: Fixed > Improve version probing of subscription info >

[jira] [Commented] (KAFKA-7174) Improve version probing of subscription info

[ https://issues.apache.org/jira/browse/KAFKA-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108476#comment-17108476 ] Guozhang Wang commented on KAFKA-7174: -- My original comment is about using a separate error code to

[jira] [Commented] (KAFKA-7041) Using RocksDB bulk loading for StandbyTasks

[ https://issues.apache.org/jira/browse/KAFKA-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107901#comment-17107901 ] Guozhang Wang commented on KAFKA-7041: -- I'd agree with your assessment, actually I'm thinking that,

[jira] [Updated] (KAFKA-10001) Store's own restore listener should be triggered in store changelog reader

[ https://issues.apache.org/jira/browse/KAFKA-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10001: -- Description: Streams' state store ``register()`` function passed in `restoreCallback` can

[jira] [Assigned] (KAFKA-10001) Store's own restore listener should be triggered in store changelog reader

[ https://issues.apache.org/jira/browse/KAFKA-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-10001: - Assignee: Guozhang Wang > Store's own restore listener should be triggered in store

[jira] [Created] (KAFKA-10001) Store's own restore listener should be triggered in store changelog reader

Guozhang Wang created KAFKA-10001: - Summary: Store's own restore listener should be triggered in store changelog reader Key: KAFKA-10001 URL: https://issues.apache.org/jira/browse/KAFKA-10001

[jira] [Commented] (KAFKA-9659) Kafka Streams / Consumer configured for static membership fails on "fatal exception: group.instance.id gets fenced"

[ https://issues.apache.org/jira/browse/KAFKA-9659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106699#comment-17106699 ] Guozhang Wang commented on KAFKA-9659: -- Hi [~lkokhreidze] Could you try out the latest trunk for

[jira] [Resolved] (KAFKA-9897) Flaky Test StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9897. -- Resolution: Fixed > Flaky Test

[jira] [Commented] (KAFKA-9984) Should fail the subscription when pattern is empty

[ https://issues.apache.org/jira/browse/KAFKA-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106549#comment-17106549 ] Guozhang Wang commented on KAFKA-9984: -- Sounds good to me :) > Should fail the subscription when

[jira] [Resolved] (KAFKA-9798) Flaky test: org.apache.kafka.streams.integration.QueryableStateIntegrationTest.shouldAllowConcurrentAccesses

[ https://issues.apache.org/jira/browse/KAFKA-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9798. -- Resolution: Not A Problem > Flaky test: >

[jira] [Commented] (KAFKA-9897) Flaky Test StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105954#comment-17105954 ] Guozhang Wang commented on KAFKA-9897: -- I'd say "yes" (biased of course :) > Flaky Test

[jira] [Commented] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105816#comment-17105816 ] Guozhang Wang commented on KAFKA-3184: -- Hello [~nizhikov] for many state-light applications, it is

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105739#comment-17105739 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Did cherry-pick this commit as well?

[jira] [Commented] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105613#comment-17105613 ] Guozhang Wang commented on KAFKA-9953: -- Thanks [~jwijgerd]. Just to clarify I'm not questioning the

[jira] [Assigned] (KAFKA-9617) Replica Fetcher can mark partition as failed when max.message.bytes is changed

[ https://issues.apache.org/jira/browse/KAFKA-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-9617: Assignee: Chia-Ping Tsai > Replica Fetcher can mark partition as failed when

[jira] [Commented] (KAFKA-9617) Replica Fetcher can mark partition as failed when max.message.bytes is changed

[ https://issues.apache.org/jira/browse/KAFKA-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104946#comment-17104946 ] Guozhang Wang commented on KAFKA-9617: -- [~chia7712] sure! I've just assigned the ticket to you,

[jira] [Commented] (KAFKA-9909) Kafka Streams : offset control to Streams API

[ https://issues.apache.org/jira/browse/KAFKA-9909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104937#comment-17104937 ] Guozhang Wang commented on KAFKA-9909: -- [~gopikrishna.chaga...@target.com] We do have future plans

[jira] [Commented] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104893#comment-17104893 ] Guozhang Wang commented on KAFKA-9953: -- [~jwijgerd] I'm curious to learn your scenario, more

<    3   4   5   6   7   8   9   10   11   12   >