[jira] [Commented] (KAFKA-6647) KafkaStreams.cleanUp creates .lock file in directory its trying to clean (Windows OS)

[ https://issues.apache.org/jira/browse/KAFKA-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056511#comment-17056511 ] Guozhang Wang commented on KAFKA-6647: -- [~shoffmeister] [~slmingol] [~lind] I have a

[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&focusedCommentId=17057241#comment-17057241 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Yes here are the current stat

[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&focusedCommentId=17057269#comment-17057269 ] Guozhang Wang commented on KAFKA-8803: -- [~oleksii.boiko] indeed had a great observat

[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&focusedCommentId=17057279#comment-17057279 ] Guozhang Wang commented on KAFKA-8803: -- https://github.com/apache/kafka/pull/8269 >

[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&focusedCommentId=17057285#comment-17057285 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] "and due to time shift which

[jira] [Comment Edited] (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&focusedCommentId=17057285#comment-17057285 ] Guozhang Wang edited comment on KAFKA-8803 at 3/11/20, 6:08 PM: ---

[jira] [Comment Edited] (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&focusedCommentId=17057285#comment-17057285 ] Guozhang Wang edited comment on KAFKA-8803 at 3/11/20, 6:09 PM: ---

[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&focusedCommentId=17057291#comment-17057291 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Also about your reported Ille

[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&focusedCommentId=17057296#comment-17057296 ] Guozhang Wang commented on KAFKA-8803: -- Raman, could you share the broker-side logs

[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&focusedCommentId=17058444#comment-17058444 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] I took some time on the logs,

[jira] [Commented] (KAFKA-5604) All producer methods should raise `ProducerFencedException` after the first time.

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059481#comment-17059481 ] Guozhang Wang commented on KAFKA-5604: -- Thank you for looking into this, and I think

[jira] [Commented] (KAFKA-6647) KafkaStreams.cleanUp creates .lock file in directory its trying to clean (Windows OS)

[ https://issues.apache.org/jira/browse/KAFKA-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059488#comment-17059488 ] Guozhang Wang commented on KAFKA-6647: -- I've pushed the fix to trunk / 2.5 which is

[jira] [Resolved] (KAFKA-6647) KafkaStreams.cleanUp creates .lock file in directory its trying to clean (Windows OS)

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

[jira] [Assigned] (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:all-tabpanel ] Guozhang Wang reassigned KAFKA-9659: Assignee: Guozhang Wang > Kafka Streams / Consumer configured for static membership fails

[jira] [Commented] (KAFKA-5604) All producer methods should raise `ProducerFencedException` after the first time.

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062006#comment-17062006 ] Guozhang Wang commented on KAFKA-5604: -- [~iamabug] There are some context missing fr

[jira] [Commented] (KAFKA-5604) All producer methods should raise `ProducerFencedException` after the first time.

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062064#comment-17062064 ] Guozhang Wang commented on KAFKA-5604: -- Verified that I've fixed the producer as in

[jira] [Resolved] (KAFKA-5604) All producer methods should raise `ProducerFencedException` after the first time.

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5604. -- Fix Version/s: 2.3.0 Assignee: Guozhang Wang (was: Apurva Mehta) Resolution: Fi

[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&focusedCommentId=17062177#comment-17062177 ] Guozhang Wang commented on KAFKA-8803: -- [~ableegoldman] I think 8858 and 8803 are re

[jira] [Commented] (KAFKA-8858) Kafka Streams - Failed to Rebalance Error and stream consumer stuck for some reason

[ https://issues.apache.org/jira/browse/KAFKA-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062178#comment-17062178 ] Guozhang Wang commented on KAFKA-8858: -- [~ableegoldman] I'm not sure I followed your

[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&focusedCommentId=17062200#comment-17062200 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Here's my current investigati

[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&focusedCommentId=17062874#comment-17062874 ] Guozhang Wang commented on KAFKA-8803: -- I guess what I tried to convey is that it's

[jira] [Resolved] (KAFKA-9701) Consumer could catch InconsistentGroupProtocolException during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9701. -- Fix Version/s: 2.5.0 Resolution: Fixed > Consumer could catch InconsistentGroupProtocolE

[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&focusedCommentId=17065190#comment-17065190 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] We found another cause that c

[jira] [Resolved] (KAFKA-6820) Improve on StreamsMetrics Public APIs

[ https://issues.apache.org/jira/browse/KAFKA-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6820. -- Resolution: Fixed > Improve on StreamsMetrics Public APIs > ---

[jira] [Created] (KAFKA-9753) Add task-level active-process-ratio to Streams metrics

Guozhang Wang created KAFKA-9753: Summary: Add task-level active-process-ratio to Streams metrics Key: KAFKA-9753 URL: https://issues.apache.org/jira/browse/KAFKA-9753 Project: Kafka Issue Ty

[jira] [Created] (KAFKA-9756) Refactor the main loop to process more than one record of one task at a time

Guozhang Wang created KAFKA-9756: Summary: Refactor the main loop to process more than one record of one task at a time Key: KAFKA-9756 URL: https://issues.apache.org/jira/browse/KAFKA-9756 Project: K

[jira] [Commented] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

[ https://issues.apache.org/jira/browse/KAFKA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066372#comment-17066372 ] Guozhang Wang commented on KAFKA-9749: -- [~bob-barrett] [~hachikuji] Just for my own

[jira] [Commented] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

[ https://issues.apache.org/jira/browse/KAFKA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066382#comment-17066382 ] Guozhang Wang commented on KAFKA-9749: -- Thanks! > TransactionMarkerRequestCompletio

[jira] [Resolved] (KAFKA-9756) Refactor the main loop to process more than one record of one task at a time

[ https://issues.apache.org/jira/browse/KAFKA-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9756. -- Fix Version/s: 2.6.0 Resolution: Fixed > Refactor the main loop to process more than one

[jira] [Resolved] (KAFKA-8937) Flaky Test SaslPlainSslEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

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

[jira] [Commented] (KAFKA-8677) Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071383#comment-17071383 ] Guozhang Wang commented on KAFKA-8677: -- I'm going to investigate the newly reported

[jira] [Comment Edited] (KAFKA-8677) Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071383#comment-17071383 ] Guozhang Wang edited comment on KAFKA-8677 at 3/31/20, 1:49 AM: ---

[jira] [Resolved] (KAFKA-9753) Add task-level active-process-ratio to Streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9753. -- Fix Version/s: 2.6.0 Resolution: Fixed > Add task-level active-process-ratio to Streams

[jira] [Resolved] (KAFKA-5842) QueryableStateIntegrationTest may fail with JDK 7

[ https://issues.apache.org/jira/browse/KAFKA-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5842. -- Resolution: Fixed Hopefully it has fixed via https://github.com/apache/kafka/pull/8370 > Query

[jira] [Resolved] (KAFKA-9783) Flaky Test QueryableStateIntegrationTest#concurrentAccesses

[ https://issues.apache.org/jira/browse/KAFKA-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9783. -- Fix Version/s: 2.6.0 Resolution: Fixed I think https://github.com/apache/kafka/pull/8370

[jira] [Created] (KAFKA-9801) Static member could get empty assignment unexpectedly

Guozhang Wang created KAFKA-9801: Summary: Static member could get empty assignment unexpectedly Key: KAFKA-9801 URL: https://issues.apache.org/jira/browse/KAFKA-9801 Project: Kafka Issue Typ

[jira] [Commented] (KAFKA-9798) org.apache.kafka.streams.integration.QueryableStateIntegrationTest.shouldAllowConcurrentAccesses

[ https://issues.apache.org/jira/browse/KAFKA-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073232#comment-17073232 ] Guozhang Wang commented on KAFKA-9798: -- {code} java.lang.AssertionError: Did not rec

[jira] [Commented] (KAFKA-9798) org.apache.kafka.streams.integration.QueryableStateIntegrationTest.shouldAllowConcurrentAccesses

[ https://issues.apache.org/jira/browse/KAFKA-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073240#comment-17073240 ] Guozhang Wang commented on KAFKA-9798: -- I pushed a hotfix commit into trunk, let's s

[jira] [Updated] (KAFKA-9801) Static member could get empty assignment unexpectedly

[ https://issues.apache.org/jira/browse/KAFKA-9801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-9801: - Description: Take the following example trace where static members are joining the group: 1. Sta

[jira] [Updated] (KAFKA-9803) Allow producers to recover gracefully from transaction timeouts

[ https://issues.apache.org/jira/browse/KAFKA-9803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-9803: - Component/s: streams consumer > Allow producers to recover gracefully from trans

[jira] [Updated] (KAFKA-9803) Allow producers to recover gracefully from transaction timeouts

[ https://issues.apache.org/jira/browse/KAFKA-9803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-9803: - Component/s: (was: consumer) producer > Allow producers to recover graceful

[jira] [Created] (KAFKA-9816) Group Coordinator should be stricter about leader returned assignment

Guozhang Wang created KAFKA-9816: Summary: Group Coordinator should be stricter about leader returned assignment Key: KAFKA-9816 URL: https://issues.apache.org/jira/browse/KAFKA-9816 Project: Kafka

[jira] [Created] (KAFKA-9821) Partition may skip assignment with static members and incremental rebalances

Guozhang Wang created KAFKA-9821: Summary: Partition may skip assignment with static members and incremental rebalances Key: KAFKA-9821 URL: https://issues.apache.org/jira/browse/KAFKA-9821 Project: K

[jira] [Commented] (KAFKA-9821) Partition may skip assignment with static members and incremental rebalances

[ https://issues.apache.org/jira/browse/KAFKA-9821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075220#comment-17075220 ] Guozhang Wang commented on KAFKA-9821: -- Yup I totally agree with the logging improve

[jira] [Created] (KAFKA-9823) Consumer should check equality of the generation for coordinator requests

Guozhang Wang created KAFKA-9823: Summary: Consumer should check equality of the generation for coordinator requests Key: KAFKA-9823 URL: https://issues.apache.org/jira/browse/KAFKA-9823 Project: Kafk

[jira] [Updated] (KAFKA-9811) TransactionMetadata state and pendingState are non-volatile and read outside the metadata lock

[ https://issues.apache.org/jira/browse/KAFKA-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-9811: - Component/s: core > TransactionMetadata state and pendingState are non-volatile and read outside

[jira] [Commented] (KAFKA-10309) KafkaProducer's sendOffsetsToTransaction should not block infinitively

[ https://issues.apache.org/jira/browse/KAFKA-10309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166022#comment-17166022 ] Guozhang Wang commented on KAFKA-10309: --- Thanks for catching this. I'd agree that

[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&focusedCommentId=17166038#comment-17166038 ] Guozhang Wang commented on KAFKA-10134: --- What I did not see from my local run is t

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166090#comment-17166090 ] Guozhang Wang commented on KAFKA-8037: -- Thank you all for providing your thoughts! I

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166602#comment-17166602 ] Guozhang Wang commented on KAFKA-8037: -- Per the interaction: I'm actually suggesting

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166762#comment-17166762 ] Guozhang Wang commented on KAFKA-8037: -- {quote} Sure, this would hold if a user spec

[jira] [Commented] (KAFKA-10283) Consolidate client-level and consumer-level assignment within ClientState

[ https://issues.apache.org/jira/browse/KAFKA-10283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168100#comment-17168100 ] Guozhang Wang commented on KAFKA-10283: --- Sure [~high.lee]. I'd suggest you get fam

[jira] [Updated] (KAFKA-10336) Rolling upgrade with Suppression AND Standbys may throw exceptions

[ https://issues.apache.org/jira/browse/KAFKA-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10336: -- Labels: bug user-experience (was: ) > Rolling upgrade with Suppression AND Standbys may throw

[jira] [Commented] (KAFKA-7777) Decouple topic serdes from materialized serdes

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169176#comment-17169176 ] Guozhang Wang commented on KAFKA-: -- Another walkaround for now, is to use `KTabl

[jira] [Commented] (KAFKA-8027) Gradual decline in performance of CachingWindowStore provider when number of keys grow

[ https://issues.apache.org/jira/browse/KAFKA-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169189#comment-17169189 ] Guozhang Wang commented on KAFKA-8027: -- We encountered similar issues in our benchma

[jira] [Created] (KAFKA-10355) Handle accidental deletion of source-topics as exceptional failure

Guozhang Wang created KAFKA-10355: - Summary: Handle accidental deletion of source-topics as exceptional failure Key: KAFKA-10355 URL: https://issues.apache.org/jira/browse/KAFKA-10355 Project: Kafka

[jira] [Created] (KAFKA-10356) Handle accidental deletion of sink-topics as exceptional failure

Guozhang Wang created KAFKA-10356: - Summary: Handle accidental deletion of sink-topics as exceptional failure Key: KAFKA-10356 URL: https://issues.apache.org/jira/browse/KAFKA-10356 Project: Kafka

[jira] [Created] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

Guozhang Wang created KAFKA-10357: - Summary: Handle accidental deletion of repartition-topics as exceptional failure Key: KAFKA-10357 URL: https://issues.apache.org/jira/browse/KAFKA-10357 Project: Ka

[jira] [Created] (KAFKA-10362) When resuming Streams active task with EOS, the checkpoint file should be deleted

Guozhang Wang created KAFKA-10362: - Summary: When resuming Streams active task with EOS, the checkpoint file should be deleted Key: KAFKA-10362 URL: https://issues.apache.org/jira/browse/KAFKA-10362 P

[jira] [Resolved] (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:all-tabpanel ] Guozhang Wang resolved KAFKA-9659. -- Fix Version/s: 2.6.0 Resolution: Fixed > Kafka Streams / Consumer configured for static

[jira] [Resolved] (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 resolved KAFKA-9450. -- Fix Version/s: 2.7.0 Resolution: Fixed > Decouple inner state flushing from committing >

[jira] [Updated] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

[ https://issues.apache.org/jira/browse/KAFKA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10357: -- Description: Repartition topics are both written by Stream's producer and read by Stream's co

[jira] [Commented] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

[ https://issues.apache.org/jira/browse/KAFKA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175976#comment-17175976 ] Guozhang Wang commented on KAFKA-10357: --- [~cadonna] 1) yeah I mean STARTING; 2) in

[jira] [Created] (KAFKA-10391) Streams should overwrite checkpoint excluding corrupted partitions

Guozhang Wang created KAFKA-10391: - Summary: Streams should overwrite checkpoint excluding corrupted partitions Key: KAFKA-10391 URL: https://issues.apache.org/jira/browse/KAFKA-10391 Project: Kafka

[jira] [Commented] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

[ https://issues.apache.org/jira/browse/KAFKA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176582#comment-17176582 ] Guozhang Wang commented on KAFKA-10357: --- I've thought about relaying on the commit

[jira] [Resolved] (KAFKA-10391) Streams should overwrite checkpoint excluding corrupted partitions

[ https://issues.apache.org/jira/browse/KAFKA-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10391. --- Fix Version/s: 2.7.0 Resolution: Fixed > Streams should overwrite checkpoint excludin

[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&focusedCommentId=17180775#comment-17180775 ] Guozhang Wang commented on KAFKA-10134: --- I think I'd need more information to furt

[jira] [Commented] (KAFKA-10410) OnRestoreStart disappeared from StateRestoreCallback in 2.6.0 and reappeared in a useless place

[ https://issues.apache.org/jira/browse/KAFKA-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180811#comment-17180811 ] Guozhang Wang commented on KAFKA-10410: --- Hello [~markshelton], thanks for reportin

[jira] [Commented] (KAFKA-10362) When resuming Streams active task with EOS, the checkpoint file should be deleted

[ https://issues.apache.org/jira/browse/KAFKA-10362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181498#comment-17181498 ] Guozhang Wang commented on KAFKA-10362: --- Hi [~ipasynkov], sure! If you have read t

[jira] [Commented] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

[ https://issues.apache.org/jira/browse/KAFKA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183626#comment-17183626 ] Guozhang Wang commented on KAFKA-10357: --- Theoretically, I think today there's no p

[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&focusedCommentId=17183654#comment-17183654 ] Guozhang Wang commented on KAFKA-10134: --- [~zhowei] Thanks for the new log files, i

[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&focusedCommentId=17184837#comment-17184837 ] Guozhang Wang commented on KAFKA-10134: --- [~zhowei] could you try out https://githu

[jira] [Commented] (KAFKA-10410) OnRestoreStart disappeared from StateRestoreCallback in 2.6.0 and reappeared in a useless place

[ https://issues.apache.org/jira/browse/KAFKA-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185367#comment-17185367 ] Guozhang Wang commented on KAFKA-10410: --- Not sure if I fully understand what do yo

[jira] [Commented] (KAFKA-10410) OnRestoreStart disappeared from StateRestoreCallback in 2.6.0 and reappeared in a useless place

[ https://issues.apache.org/jira/browse/KAFKA-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186019#comment-17186019 ] Guozhang Wang commented on KAFKA-10410: --- Thanks Mark for your explanation. I think

[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&focusedCommentId=17188116#comment-17188116 ] Guozhang Wang commented on KAFKA-10134: --- Hello [~zhowei] that broker-side change i

[jira] [Commented] (KAFKA-10455) Probing rebalances are not guaranteed to be triggered by non-leader members

[ https://issues.apache.org/jira/browse/KAFKA-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189843#comment-17189843 ] Guozhang Wang commented on KAFKA-10455: --- I'm trying to assess statistically how la

[jira] [Commented] (KAFKA-10455) Probing rebalances are not guaranteed to be triggered by non-leader members

[ https://issues.apache.org/jira/browse/KAFKA-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192371#comment-17192371 ] Guozhang Wang commented on KAFKA-10455: --- Thanks for the info [~ableegoldman]. I th

[jira] [Commented] (KAFKA-10465) Potential Bug/Doc update in Transactional Producer and Isolation Level

[ https://issues.apache.org/jira/browse/KAFKA-10465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193988#comment-17193988 ] Guozhang Wang commented on KAFKA-10465: --- Hello [~manme...@gmail.com] what's docume

[jira] [Commented] (KAFKA-6127) Streams should never block infinitely

[ https://issues.apache.org/jira/browse/KAFKA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194590#comment-17194590 ] Guozhang Wang commented on KAFKA-6127: -- I think we can close this ticket now, since:

[jira] [Commented] (KAFKA-10484) Reduce Metrics Exposed by Streams

[ https://issues.apache.org/jira/browse/KAFKA-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196289#comment-17196289 ] Guozhang Wang commented on KAFKA-10484: --- Thanks Bruno. I agree that providing some

[jira] [Created] (KAFKA-10485) Use a separate error code for replication related errors

Guozhang Wang created KAFKA-10485: - Summary: Use a separate error code for replication related errors Key: KAFKA-10485 URL: https://issues.apache.org/jira/browse/KAFKA-10485 Project: Kafka Is

[jira] [Commented] (KAFKA-10475) Using same key reports different count of records for groupBy() and groupByKey() in Kafka Streaming Application

[ https://issues.apache.org/jira/browse/KAFKA-10475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196462#comment-17196462 ] Guozhang Wang commented on KAFKA-10475: --- [~bchen225242] could you also help lookin

[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&focusedCommentId=17196476#comment-17196476 ] Guozhang Wang commented on KAFKA-8803: -- [~bp...@yahoo.com][~msilb][~vkorna][~eleanor

[jira] [Updated] (KAFKA-9876) Implement Raft Protocol for Metadata Quorum

[ https://issues.apache.org/jira/browse/KAFKA-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-9876: - Component/s: core > Implement Raft Protocol for Metadata Quorum > ---

[jira] [Commented] (KAFKA-10485) Use a separate error code for replication related errors

[ https://issues.apache.org/jira/browse/KAFKA-10485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198859#comment-17198859 ] Guozhang Wang commented on KAFKA-10485: --- [~chia7712] If the txn's request timeout

[jira] [Commented] (KAFKA-10493) Ktable out-of-order updates are not being ignored

[ https://issues.apache.org/jira/browse/KAFKA-10493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198861#comment-17198861 ] Guozhang Wang commented on KAFKA-10493: --- ``compareValuesAndCheckForIncreasingTimes

[jira] [Commented] (KAFKA-10493) Ktable out-of-order updates are not being ignored

[ https://issues.apache.org/jira/browse/KAFKA-10493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199688#comment-17199688 ] Guozhang Wang commented on KAFKA-10493: --- Thanks for double checking John! The PR l

[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&focusedCommentId=17202931#comment-17202931 ] Guozhang Wang commented on KAFKA-10134: --- I don't think there's a concrete plan for

[jira] [Updated] (KAFKA-10502) Threadlocal may can not set null,because it may create a memory leak

[ https://issues.apache.org/jira/browse/KAFKA-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10502: -- Description: When setting Threadlocal to null it may create a memory leak, you can see the li

[jira] [Resolved] (KAFKA-10502) Threadlocal may can not set null,because it may create a memory leak

[ https://issues.apache.org/jira/browse/KAFKA-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10502. --- Fix Version/s: 2.7.0 Resolution: Fixed > Threadlocal may can not set null,because it

[jira] [Commented] (KAFKA-10513) Newly added topic or partitions are not assigned to running consumer groups using static membership

[ https://issues.apache.org/jira/browse/KAFKA-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202991#comment-17202991 ] Guozhang Wang commented on KAFKA-10513: --- This seems to be a valid issue after read

[jira] [Created] (KAFKA-10532) Do not wipe state store under EOS when closing a RESTORING active or RUNNING standby task

Guozhang Wang created KAFKA-10532: - Summary: Do not wipe state store under EOS when closing a RESTORING active or RUNNING standby task Key: KAFKA-10532 URL: https://issues.apache.org/jira/browse/KAFKA-10532

[jira] [Updated] (KAFKA-10532) Do not wipe state store under EOS when closing-dirty a RESTORING active or RUNNING standby task

[ https://issues.apache.org/jira/browse/KAFKA-10532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10532: -- Summary: Do not wipe state store under EOS when closing-dirty a RESTORING active or RUNNING st

[jira] [Updated] (KAFKA-10532) Do not wipe state store under EOS when closing-dirty a RESTORING active or RUNNING standby task

[ https://issues.apache.org/jira/browse/KAFKA-10532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10532: -- Description: Today whenever we are closing-dirty a task, we always wipe out the state stores i

[jira] [Commented] (KAFKA-10513) Newly added topic or partitions are not assigned to running consumer groups using static membership

[ https://issues.apache.org/jira/browse/KAFKA-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203622#comment-17203622 ] Guozhang Wang commented on KAFKA-10513: --- [~mou@ea] could you try setting the `meta

[jira] [Resolved] (KAFKA-9061) StreamStreamJoinIntegrationTest flaky test failures

[ https://issues.apache.org/jira/browse/KAFKA-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9061. -- Resolution: Cannot Reproduce > StreamStreamJoinIntegrationTest flaky test failures > --

[jira] [Commented] (KAFKA-9061) StreamStreamJoinIntegrationTest flaky test failures

[ https://issues.apache.org/jira/browse/KAFKA-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204301#comment-17204301 ] Guozhang Wang commented on KAFKA-9061: -- I have not seen this failure for a while, wi

[jira] [Resolved] (KAFKA-10326) Both serializer and deserializer should be able to see the generated client id

[ https://issues.apache.org/jira/browse/KAFKA-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10326. --- Fix Version/s: 2.7.0 Resolution: Fixed > Both serializer and deserializer should be a

[jira] [Commented] (KAFKA-10465) Potential Bug/Doc update in Transactional Producer and Isolation Level

[ https://issues.apache.org/jira/browse/KAFKA-10465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205236#comment-17205236 ] Guozhang Wang commented on KAFKA-10465: --- Hi [~manme...@gmail.com], hmm that is ind

[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&focusedCommentId=17205244#comment-17205244 ] Guozhang Wang commented on KAFKA-6579: -- Yup, go ahead! > Consolidate window store a

<    1   2   3   4   5   6   7   8   9   10   >