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

[ https://issues.apache.org/jira/browse/KAFKA-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227080#comment-17227080 ] Guozhang Wang commented on KAFKA-10688: --- Without KAFKA-3370, then we have to implement the desired

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

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

[jira] [Commented] (KAFKA-1800) KafkaException was not recorded at the per-topic metrics

[ https://issues.apache.org/jira/browse/KAFKA-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226934#comment-17226934 ] Guozhang Wang commented on KAFKA-1800: -- This has been fixed since 1.0.0; closing now. >

[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=17221813#comment-17221813 ] Guozhang Wang commented on KAFKA-8803: -- [~pdeole] I was OOO and just saw your message. So far all

[jira] [Resolved] (KAFKA-10616) StreamThread killed by "IllegalStateException: The processor is already closed"

[ https://issues.apache.org/jira/browse/KAFKA-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10616. --- Resolution: Fixed > StreamThread killed by "IllegalStateException: The processor is already

[jira] [Commented] (KAFKA-10616) StreamThread killed by "IllegalStateException: The processor is already closed"

[ https://issues.apache.org/jira/browse/KAFKA-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17217813#comment-17217813 ] Guozhang Wang commented on KAFKA-10616: --- I think this is a long lurking bug caused by

[jira] [Comment Edited] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17214839#comment-17214839 ] Guozhang Wang edited comment on KAFKA-10613 at 10/15/20, 5:07 PM: -- When

[jira] [Updated] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10613: -- Affects Version/s: 2.1.0 2.2.0 2.3.0

[jira] [Updated] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10613: -- Issue Type: Bug (was: Improvement) > Broker should not set leader epoch if the list-offset

[jira] [Resolved] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10613. --- Fix Version/s: 2.7.0 Resolution: Fixed > Broker should not set leader epoch if the

[jira] [Updated] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10613: -- Component/s: (was: streams) core > Broker should not set leader epoch if

[jira] [Commented] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

[ https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17214839#comment-17214839 ] Guozhang Wang commented on KAFKA-10613: --- When we introduce the new version 4 in list-offsets I

[jira] [Created] (KAFKA-10614) Group coordinator onElection/onResignation should guard against leader epoch

Guozhang Wang created KAFKA-10614: - Summary: Group coordinator onElection/onResignation should guard against leader epoch Key: KAFKA-10614 URL: https://issues.apache.org/jira/browse/KAFKA-10614

[jira] [Created] (KAFKA-10613) Broker should not set leader epoch if the list-offset request version < 4

Guozhang Wang created KAFKA-10613: - Summary: Broker should not set leader epoch if the list-offset request version < 4 Key: KAFKA-10613 URL: https://issues.apache.org/jira/browse/KAFKA-10613 Project:

[jira] [Updated] (KAFKA-10585) Kafka Streams should clean up the state store directory from cleanup

[ https://issues.apache.org/jira/browse/KAFKA-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-10585: -- Labels: newbie++ (was: ) > Kafka Streams should clean up the state store directory from

[jira] [Resolved] (KAFKA-10271) Performance regression while fetching a key from a single partition

[ https://issues.apache.org/jira/browse/KAFKA-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10271. --- Fix Version/s: (was: 2.5.2) 2.7.0 Resolution: Fixed >

[jira] [Resolved] (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:all-tabpanel ] Guozhang Wang resolved KAFKA-10362. --- Fix Version/s: 2.7.0 Resolution: Fixed > When resuming Streams active task with EOS,

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

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

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

[ https://issues.apache.org/jira/browse/KAFKA-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209685#comment-17209685 ] Guozhang Wang commented on KAFKA-10122: --- This ticket is resolved as a result of KAFKA-10134: when

[jira] [Created] (KAFKA-10577) StreamThread should be able to process any processible tasks regardless of its state

Guozhang Wang created KAFKA-10577: - Summary: StreamThread should be able to process any processible tasks regardless of its state Key: KAFKA-10577 URL: https://issues.apache.org/jira/browse/KAFKA-10577

[jira] [Created] (KAFKA-10575) StateRestoreListener#onRestoreEnd should always be triggered

Guozhang Wang created KAFKA-10575: - Summary: StateRestoreListener#onRestoreEnd should always be triggered Key: KAFKA-10575 URL: https://issues.apache.org/jira/browse/KAFKA-10575 Project: Kafka

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

[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=17205236#comment-17205236 ] Guozhang Wang commented on KAFKA-10465: --- Hi [~manme...@gmail.com], hmm that is indeed a bit weird.

[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

[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=17204301#comment-17204301 ] Guozhang Wang commented on KAFKA-9061: -- I have not seen this failure for a while, will close it for

[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=17203622#comment-17203622 ] Guozhang Wang commented on KAFKA-10513: --- [~mou@ea] could you try setting the `metadata.max.age.ms`

[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

[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

[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] [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=17202991#comment-17202991 ] Guozhang Wang commented on KAFKA-10513: --- This seems to be a valid issue after reading the source

[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

[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

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

[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=17199688#comment-17199688 ] Guozhang Wang commented on KAFKA-10493: --- Thanks for double checking John! The PR lgtm too.

[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=17198861#comment-17198861 ] Guozhang Wang commented on KAFKA-10493: --- ``compareValuesAndCheckForIncreasingTimestamp`` is added

[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=17198859#comment-17198859 ] Guozhang Wang commented on KAFKA-10485: --- [~chia7712] If the txn's request timeout value is used as

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

[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=17196462#comment-17196462 ] Guozhang Wang commented on KAFKA-10475: --- [~bchen225242] could you also help looking into whether

[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

[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=17196289#comment-17196289 ] Guozhang Wang commented on KAFKA-10484: --- Thanks Bruno. I agree that providing some higher-level

[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=17194590#comment-17194590 ] Guozhang Wang commented on KAFKA-6127: -- I think we can close this ticket now, since: * All blocking

[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=17193988#comment-17193988 ] Guozhang Wang commented on KAFKA-10465: --- Hello [~manme...@gmail.com] what's documented is correct:

[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=17192371#comment-17192371 ] Guozhang Wang commented on KAFKA-10455: --- Thanks for the info [~ableegoldman]. I think we can have

[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=17189843#comment-17189843 ] Guozhang Wang commented on KAFKA-10455: --- I'm trying to assess statistically how large this may

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

[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=17186019#comment-17186019 ] Guozhang Wang commented on KAFKA-10410: --- Thanks Mark for your explanation. I think for metrics

[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=17185367#comment-17185367 ] Guozhang Wang commented on KAFKA-10410: --- Not sure if I fully understand what do you mean by

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

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

[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=17183626#comment-17183626 ] Guozhang Wang commented on KAFKA-10357: --- Theoretically, I think today there's no perfect solution

[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=17181498#comment-17181498 ] Guozhang Wang commented on KAFKA-10362: --- Hi [~ipasynkov], sure! If you have read through the

[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=17180811#comment-17180811 ] Guozhang Wang commented on KAFKA-10410: --- Hello [~markshelton], thanks for reporting this. Yes

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

[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

[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=17176582#comment-17176582 ] Guozhang Wang commented on KAFKA-10357: --- I've thought about relaying on the committed offsets, but

[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=17175976#comment-17175976 ] Guozhang Wang commented on KAFKA-10357: --- [~cadonna] 1) yeah I mean STARTING; 2) in practice newly

[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

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

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

[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-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] [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=17169189#comment-17169189 ] Guozhang Wang commented on KAFKA-8027: -- We encountered similar issues in our benchmarks which is

[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=17169176#comment-17169176 ] Guozhang Wang commented on KAFKA-: -- Another walkaround for now, is to use `KTable#mapValues()`

[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

[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=17168100#comment-17168100 ] Guozhang Wang commented on KAFKA-10283: --- Sure [~high.lee]. I'd suggest you get familiar with the

[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=17166762#comment-17166762 ] Guozhang Wang commented on KAFKA-8037: -- {quote} Sure, this would hold if a user specifies the new

[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=17166602#comment-17166602 ] Guozhang Wang commented on KAFKA-8037: -- Per the interaction: I'm actually suggesting that the

[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=17166090#comment-17166090 ] Guozhang Wang commented on KAFKA-8037: -- Thank you all for providing your thoughts! In consolidating

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

[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=17166022#comment-17166022 ] Guozhang Wang commented on KAFKA-10309: --- Thanks for catching this. I'd agree that any blocking

[jira] [Commented] (KAFKA-10284) Group membership update due to static member rejoin should be persisted

[ https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164063#comment-17164063 ] Guozhang Wang commented on KAFKA-10284: --- What [~ableegoldman] described seems aligned to this, BUT

[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=17163761#comment-17163761 ] Guozhang Wang commented on KAFKA-10134: --- BTW I found that the main latency during rebalance is on

[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=17163759#comment-17163759 ] Guozhang Wang commented on KAFKA-10134: --- [~zhowei] Did your run include both the log4j improvement

[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=17163204#comment-17163204 ] Guozhang Wang commented on KAFKA-8037: -- Here's a wild thought following [~agavra]'s last comment:

[jira] [Comment Edited] (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=17163134#comment-17163134 ] Guozhang Wang edited comment on KAFKA-8037 at 7/22/20, 11:22 PM: - Great

[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=17163134#comment-17163134 ] Guozhang Wang commented on KAFKA-8037: -- Great comments from all of you, thank you so much! I'd like

[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=17163002#comment-17163002 ] Guozhang Wang commented on KAFKA-8037: -- Hey guys thanks for your input. I think [~vvcephei] has a

[jira] [Comment Edited] (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=17161565#comment-17161565 ] Guozhang Wang edited comment on KAFKA-8037 at 7/20/20, 9:54 PM: There are

[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=17161565#comment-17161565 ] Guozhang Wang commented on KAFKA-8037: -- There are some more discussions on related issues in

[jira] [Commented] (KAFKA-10179) State Store Passes Wrong Changelog Topic to Serde for Optimized Source Tables

[ https://issues.apache.org/jira/browse/KAFKA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161423#comment-17161423 ] Guozhang Wang commented on KAFKA-10179: --- I agree with Almog and Rohan’s arguments here. What I’m

[jira] [Created] (KAFKA-10294) Consider whether some of ProcessorStateException should be auto-handled by Streams

Guozhang Wang created KAFKA-10294: - Summary: Consider whether some of ProcessorStateException should be auto-handled by Streams Key: KAFKA-10294 URL: https://issues.apache.org/jira/browse/KAFKA-10294

[jira] [Commented] (KAFKA-10284) Group membership update due to static member rejoin should be persisted

[ https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17160225#comment-17160225 ] Guozhang Wang commented on KAFKA-10284: --- Fair enough. So it seems not a correctness breaking issue

[jira] [Commented] (KAFKA-10284) Group membership update due to static member rejoin should be persisted

[ https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17160152#comment-17160152 ] Guozhang Wang commented on KAFKA-10284: --- [~bchen225242] Thanks for the find. Just trying to

[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=17160146#comment-17160146 ] Guozhang Wang commented on KAFKA-10134: --- [~zhowei] [~seanguo] I tried to reproduce your high CPU

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

Guozhang Wang created KAFKA-10283: - Summary: Consolidate client-level and consumer-level assignment within ClientState Key: KAFKA-10283 URL: https://issues.apache.org/jira/browse/KAFKA-10283 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=17156368#comment-17156368 ] Guozhang Wang commented on KAFKA-10134: --- [~zhowei] Just to clarify are you working with [~seanguo]

[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=17155659#comment-17155659 ] Guozhang Wang commented on KAFKA-10134: --- Hmm, interesting. What setup are you using with the local

[jira] [Created] (KAFKA-10263) Do not create standbys for those revoking active tasks if it is not stateful

Guozhang Wang created KAFKA-10263: - Summary: Do not create standbys for those revoking active tasks if it is not stateful Key: KAFKA-10263 URL: https://issues.apache.org/jira/browse/KAFKA-10263

[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=17153862#comment-17153862 ] Guozhang Wang commented on KAFKA-10134: --- cc 2.5.1 release manager [~vvcephei] I'm merging it to

[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=17153861#comment-17153861 ] Guozhang Wang commented on KAFKA-10134: --- Thanks for the confirmation! I'm resolving this ticket

[jira] [Resolved] (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 resolved KAFKA-10134. --- Resolution: Fixed > High CPU issue during rebalance in Kafka consumer after upgrading to

[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=17153757#comment-17153757 ] Guozhang Wang commented on KAFKA-10134: --- I've merged the PR and would like [~seanguo] [~neowu0] to

[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=17152912#comment-17152912 ] Guozhang Wang commented on KAFKA-10229: --- Thanks, please feel free to update this ticket if you

[jira] [Commented] (KAFKA-10166) Excessive TaskCorruptedException seen in testing

[ https://issues.apache.org/jira/browse/KAFKA-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152381#comment-17152381 ] Guozhang Wang commented on KAFKA-10166: --- I've merged in [~ableegoldman]'s PR, and [~cadonna] has

[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=17152377#comment-17152377 ] Guozhang Wang commented on KAFKA-10017: --- Thanks for the confirmation Sophie! I'm closing it now.

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