[jira] [Commented] (KAFKA-10772) java.lang.IllegalStateException: There are insufficient bytes available to read assignment from the sync-group response (actual byte size 0)

[ https://issues.apache.org/jira/browse/KAFKA-10772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17245586#comment-17245586 ] A. Sophie Blee-Goldman commented on KAFKA-10772: Hey [~lkokhreidze] and/or

[jira] [Commented] (KAFKA-10772) java.lang.IllegalStateException: There are insufficient bytes available to read assignment from the sync-group response (actual byte size 0)

[ https://issues.apache.org/jira/browse/KAFKA-10772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17245587#comment-17245587 ] A. Sophie Blee-Goldman commented on KAFKA-10772: Specifically, I'm looking for the log

[jira] [Commented] (KAFKA-10643) Static membership - repetitive PreparingRebalance with updating metadata for member reason

[ https://issues.apache.org/jira/browse/KAFKA-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17237660#comment-17237660 ] A. Sophie Blee-Goldman commented on KAFKA-10643: Sorry yeah I meant debug logs for the

[jira] [Assigned] (KAFKA-10758) Kafka Streams consuming from a pattern goes to PENDING_SHUTDOWN when adding a new topic

[ https://issues.apache.org/jira/browse/KAFKA-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reassigned KAFKA-10758: -- Assignee: A. Sophie Blee-Goldman > Kafka Streams consuming from a

[jira] [Commented] (KAFKA-10772) java.lang.IllegalStateException: There are insufficient bytes available to read assignment from the sync-group response (actual byte size 0)

[ https://issues.apache.org/jira/browse/KAFKA-10772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241814#comment-17241814 ] A. Sophie Blee-Goldman commented on KAFKA-10772: Hey [~lkokhreidze], thanks for the

[jira] [Commented] (KAFKA-10758) Kafka Streams consuming from a pattern goes to PENDING_SHUTDOWN when adding a new topic

[ https://issues.apache.org/jira/browse/KAFKA-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17237778#comment-17237778 ] A. Sophie Blee-Goldman commented on KAFKA-10758: Hey [~davideicardi], thanks for

[jira] [Updated] (KAFKA-10758) Kafka Streams consuming from a pattern goes to PENDING_SHUTDOWN when adding a new topic

[ https://issues.apache.org/jira/browse/KAFKA-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10758: --- Fix Version/s: 2.6.1 2.7.0 > Kafka Streams consuming

[jira] [Updated] (KAFKA-10758) Kafka Streams consuming from a pattern goes to PENDING_SHUTDOWN when adding a new topic

[ https://issues.apache.org/jira/browse/KAFKA-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10758: --- Priority: Blocker (was: Major) > Kafka Streams consuming from a pattern

[jira] [Commented] (KAFKA-10862) kafak stream consume from the earliest by default

[ https://issues.apache.org/jira/browse/KAFKA-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250720#comment-17250720 ] A. Sophie Blee-Goldman commented on KAFKA-10862: Hey [~rebekkaxi], you're looking at the

[jira] [Commented] (KAFKA-10643) Static membership - repetitive PreparingRebalance with updating metadata for member reason

[ https://issues.apache.org/jira/browse/KAFKA-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229574#comment-17229574 ] A. Sophie Blee-Goldman commented on KAFKA-10643: Ok, it sounds like maybe you do have

[jira] [Commented] (KAFKA-10716) Streams processId is unstable across restarts resulting in task mass migration

[ https://issues.apache.org/jira/browse/KAFKA-10716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231116#comment-17231116 ] A. Sophie Blee-Goldman commented on KAFKA-10716: There are a few possible ways forward

[jira] [Created] (KAFKA-10716) Streams processId is unstable across restarts resulting in task mass migration

A. Sophie Blee-Goldman created KAFKA-10716: -- Summary: Streams processId is unstable across restarts resulting in task mass migration Key: KAFKA-10716 URL:

[jira] [Commented] (KAFKA-10678) Re-deploying Streams app causes rebalance and task migration

[ https://issues.apache.org/jira/browse/KAFKA-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231084#comment-17231084 ] A. Sophie Blee-Goldman commented on KAFKA-10678: Yeah, it seems like anytime a member is

[jira] [Updated] (KAFKA-10705) Avoid World Readable RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10705: --- Fix Version/s: 2.7.1 2.8.0 > Avoid World Readable

[jira] [Commented] (KAFKA-10405) Flaky Test org.apache.kafka.streams.integration.PurgeRepartitionTopicIntegrationTest.shouldRestoreState

[ https://issues.apache.org/jira/browse/KAFKA-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231709#comment-17231709 ] A. Sophie Blee-Goldman commented on KAFKA-10405:

[jira] [Created] (KAFKA-10721) Rewrite topology to allow for overlapping unequal topic subscriptions

A. Sophie Blee-Goldman created KAFKA-10721: -- Summary: Rewrite topology to allow for overlapping unequal topic subscriptions Key: KAFKA-10721 URL: https://issues.apache.org/jira/browse/KAFKA-10721

[jira] [Updated] (KAFKA-6687) Allow to read a topic multiple times

[ https://issues.apache.org/jira/browse/KAFKA-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-6687: -- Fix Version/s: 2.8.0 > Allow to read a topic multiple times >

[jira] [Resolved] (KAFKA-10705) Avoid World Readable RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-10705. Resolution: Fixed > Avoid World Readable RocksDB >

[jira] [Updated] (KAFKA-10705) Avoid World Readable RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10705: --- Fix Version/s: 2.6.2 > Avoid World Readable RocksDB >

[jira] [Resolved] (KAFKA-7107) Ability to configure state store for JoinWindows in KStream-KStream join

[ https://issues.apache.org/jira/browse/KAFKA-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-7107. --- Resolution: Duplicate > Ability to configure state store for JoinWindows in

[jira] [Commented] (KAFKA-10721) Rewrite topology to allow for overlapping unequal topic subscriptions

[ https://issues.apache.org/jira/browse/KAFKA-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231904#comment-17231904 ] A. Sophie Blee-Goldman commented on KAFKA-10721: I agree. However, there may be more

[jira] [Commented] (KAFKA-10643) Static membership - repetitive PreparingRebalance with updating metadata for member reason

[ https://issues.apache.org/jira/browse/KAFKA-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236547#comment-17236547 ] A. Sophie Blee-Goldman commented on KAFKA-10643: Hey [~eran-levy] Thanks for uploading

[jira] [Updated] (KAFKA-6943) Have option to shutdown KS cleanly if any threads crashes, or if all threads crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-6943: -- Fix Version/s: 2.8.0 > Have option to shutdown KS cleanly if any threads

[jira] [Resolved] (KAFKA-6943) Have option to shutdown KS cleanly if any threads crashes, or if all threads crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-6943. --- Resolution: Fixed > Have option to shutdown KS cleanly if any threads

[jira] [Commented] (KAFKA-6943) Have option to shutdown KS cleanly if any threads crashes, or if all threads crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235069#comment-17235069 ] A. Sophie Blee-Goldman commented on KAFKA-6943: --- Resolved via 

[jira] [Reopened] (KAFKA-10500) Add API to Start and Stop Stream Threads

[ https://issues.apache.org/jira/browse/KAFKA-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reopened KAFKA-10500: > Add API to Start and Stop Stream Threads >

[jira] [Updated] (KAFKA-4748) Need a way to shutdown all workers in a Streams application at the same time

[ https://issues.apache.org/jira/browse/KAFKA-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-4748: -- Fix Version/s: 2.8.0 > Need a way to shutdown all workers in a Streams

[jira] [Resolved] (KAFKA-4748) Need a way to shutdown all workers in a Streams application at the same time

[ https://issues.apache.org/jira/browse/KAFKA-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-4748. --- Resolution: Fixed > Need a way to shutdown all workers in a Streams

[jira] [Commented] (KAFKA-10643) Static membership - repetitive PreparingRebalance with updating metadata for member reason

[ https://issues.apache.org/jira/browse/KAFKA-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225073#comment-17225073 ] A. Sophie Blee-Goldman commented on KAFKA-10643: Can you be a little more specific about

[jira] [Created] (KAFKA-10665) Flaky Test StreamTableJoinTopologyOptimizationIntegrationTest.shouldDoStreamTableJoinWithDifferentNumberOfPartitions[Optimization = all]

A. Sophie Blee-Goldman created KAFKA-10665: -- Summary: Flaky Test StreamTableJoinTopologyOptimizationIntegrationTest.shouldDoStreamTableJoinWithDifferentNumberOfPartitions[Optimization = all] Key: KAFKA-10665

[jira] [Created] (KAFKA-10689) Assignor can't determine number of partitions on FJK with upstream windowed repartition

A. Sophie Blee-Goldman created KAFKA-10689: -- Summary: Assignor can't determine number of partitions on FJK with upstream windowed repartition Key: KAFKA-10689 URL:

[jira] [Commented] (KAFKA-10678) Re-deploying Streams app causes rebalance and task migration

[ https://issues.apache.org/jira/browse/KAFKA-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227067#comment-17227067 ] A. Sophie Blee-Goldman commented on KAFKA-10678: Thanks for opening a separate ticket

[jira] [Commented] (KAFKA-10689) Assignor can't determine number of partitions on FJK with upstream windowed repartition

[ https://issues.apache.org/jira/browse/KAFKA-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227077#comment-17227077 ] A. Sophie Blee-Goldman commented on KAFKA-10689: It's a pretty obnoxious bug, since the

[jira] [Assigned] (KAFKA-10689) Assignor can't determine number of partitions on FJK with upstream windowed repartition

[ https://issues.apache.org/jira/browse/KAFKA-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reassigned KAFKA-10689: -- Assignee: A. Sophie Blee-Goldman > Assignor can't determine number

[jira] [Updated] (KAFKA-10689) Assignor can't determine number of partitions on FJK with upstream windowed repartition

[ https://issues.apache.org/jira/browse/KAFKA-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10689: --- Priority: Critical (was: Major) > Assignor can't determine number of

[jira] [Created] (KAFKA-10664) Streams fails to overwrite corrupted offsets leading to infinite OffsetOutOfRangeException loop

A. Sophie Blee-Goldman created KAFKA-10664: -- Summary: Streams fails to overwrite corrupted offsets leading to infinite OffsetOutOfRangeException loop Key: KAFKA-10664 URL:

[jira] [Updated] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12190: --- Affects Version/s: (was: 2.7.1) 2.7.0 > Failure

[jira] [Commented] (KAFKA-10847) Avoid spurious left/outer join results in stream-stream join

[ https://issues.apache.org/jira/browse/KAFKA-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17271698#comment-17271698 ] A. Sophie Blee-Goldman commented on KAFKA-10847: Hey [~spena] – to answer your question

[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=17271767#comment-17271767 ] A. Sophie Blee-Goldman commented on KAFKA-8803: --- Hey [~nvolynets] thanks for the report.

[jira] [Updated] (KAFKA-12219) Potential race condition in InMemoryKeyValueStore

[ https://issues.apache.org/jira/browse/KAFKA-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12219: --- Affects Version/s: 2.7.0 > Potential race condition in

[jira] [Updated] (KAFKA-12219) Potential race condition in InMemoryKeyValueStore

[ https://issues.apache.org/jira/browse/KAFKA-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12219: --- Description: With KAFKA-8802 (included in [2.4.0

[jira] [Updated] (KAFKA-12219) Potential race condition in InMemoryKeyValueStore

[ https://issues.apache.org/jira/browse/KAFKA-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12219: --- Fix Version/s: 2.7.1 > Potential race condition in InMemoryKeyValueStore >

[jira] [Updated] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12190: --- Component/s: streams > Failure on Windows due to an

[jira] [Updated] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12190: --- Priority: Critical (was: Major) > Failure on Windows due to an

[jira] [Commented] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264398#comment-17264398 ] A. Sophie Blee-Goldman commented on KAFKA-12190: Hey [~awilkinson], thanks for the bug

[jira] [Updated] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12190: --- Fix Version/s: 2.8.0 > Failure on Windows due to an

[jira] [Commented] (KAFKA-12184) Once the Error Classification is better update the default streams uncaught exception handler to replace threads

[ https://issues.apache.org/jira/browse/KAFKA-12184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263776#comment-17263776 ] A. Sophie Blee-Goldman commented on KAFKA-12184: Should we mark the "Fix Version" as 2.8

[jira] [Updated] (KAFKA-10793) Race condition in FindCoordinatorFuture permanently severs connection to group coordinator

[ https://issues.apache.org/jira/browse/KAFKA-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10793: --- Fix Version/s: 2.6.2 > Race condition in FindCoordinatorFuture permanently

[jira] [Updated] (KAFKA-8930) MM2 documentation

[ https://issues.apache.org/jira/browse/KAFKA-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-8930: -- Fix Version/s: (was: 2.6.0) 2.6.2 > MM2 documentation >

[jira] [Commented] (KAFKA-8930) MM2 documentation

[ https://issues.apache.org/jira/browse/KAFKA-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17275292#comment-17275292 ] A. Sophie Blee-Goldman commented on KAFKA-8930: --- Hey [~miguno] I changed the FixVersion to

[jira] [Updated] (KAFKA-8940) Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-8940: -- Description: The test does not properly account for windowing. See [this

[jira] [Updated] (KAFKA-8940) Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-8940: -- Labels: flaky-test newbie++ (was: flaky-test) > Flaky Test

[jira] [Updated] (KAFKA-8940) Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-8940: -- Description: The test does not properly account for windowing. See (was: I

[jira] [Updated] (KAFKA-8940) Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-8940: -- Description: The test does not properly account for windowing. See this

[jira] [Updated] (KAFKA-10340) Source connectors should report error when trying to produce records to non-existent topics instead of hanging forever

[ https://issues.apache.org/jira/browse/KAFKA-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10340: --- Fix Version/s: 2.6.2 > Source connectors should report error when trying to

[jira] [Created] (KAFKA-12288) Remove task-level filesystem locks

A. Sophie Blee-Goldman created KAFKA-12288: -- Summary: Remove task-level filesystem locks Key: KAFKA-12288 URL: https://issues.apache.org/jira/browse/KAFKA-12288 Project: Kafka Issue

[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=17272388#comment-17272388 ] A. Sophie Blee-Goldman commented on KAFKA-8803: --- Ah, yeah, then it sounds like you may be

[jira] [Updated] (KAFKA-10716) Streams processId is unstable across restarts resulting in task mass migration

[ https://issues.apache.org/jira/browse/KAFKA-10716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10716: --- Fix Version/s: 2.6.2 > Streams processId is unstable across restarts

[jira] [Updated] (KAFKA-10716) Streams processId is unstable across restarts resulting in task mass migration

[ https://issues.apache.org/jira/browse/KAFKA-10716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10716: --- Priority: Critical (was: Major) > Streams processId is unstable across

[jira] [Commented] (KAFKA-12169) Consumer can not know paritions chage when client leader restart with static membership protocol

[ https://issues.apache.org/jira/browse/KAFKA-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17273158#comment-17273158 ] A. Sophie Blee-Goldman commented on KAFKA-12169: hey [~boyang] any thoughts? > Consumer

[jira] [Assigned] (KAFKA-10716) Streams processId is unstable across restarts resulting in task mass migration

[ https://issues.apache.org/jira/browse/KAFKA-10716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reassigned KAFKA-10716: -- Assignee: A. Sophie Blee-Goldman > Streams processId is unstable

[jira] [Updated] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12190: --- Fix Version/s: 2.6.2 > Failure on Windows due to an

[jira] [Updated] (KAFKA-10716) Streams processId is unstable across restarts resulting in task mass migration

[ https://issues.apache.org/jira/browse/KAFKA-10716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-10716: --- Fix Version/s: 2.7.1 2.8.0 > Streams processId is

[jira] [Resolved] (KAFKA-10793) Race condition in FindCoordinatorFuture permanently severs connection to group coordinator

[ https://issues.apache.org/jira/browse/KAFKA-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-10793. Fix Version/s: 2.7.1 Resolution: Fixed > Race condition in

[jira] [Closed] (KAFKA-12190) Failure on Windows due to an UnsupportedOperationException when StateDirectory sets file permissions

[ https://issues.apache.org/jira/browse/KAFKA-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman closed KAFKA-12190. -- > Failure on Windows due to an UnsupportedOperationException when >

[jira] [Closed] (KAFKA-10867) Implement improved semantics using the ConsumerRecords meta

[ https://issues.apache.org/jira/browse/KAFKA-10867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman closed KAFKA-10867. -- > Implement improved semantics using the ConsumerRecords meta >

[jira] [Closed] (KAFKA-9176) Flaky test failure: OptimizedKTableIntegrationTest.shouldApplyUpdatesToStandbyStore

[ https://issues.apache.org/jira/browse/KAFKA-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman closed KAFKA-9176. - > Flaky test failure: >

[jira] [Updated] (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 ] A. Sophie Blee-Goldman updated KAFKA-10362: --- Fix Version/s: 2.6.2 > When resuming Streams active task with EOS, the

[jira] [Commented] (KAFKA-8295) Optimize count() using RocksDB merge operator

[ https://issues.apache.org/jira/browse/KAFKA-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363356#comment-17363356 ] A. Sophie Blee-Goldman commented on KAFKA-8295: --- Yes, any of the count DSL operators. It

[jira] [Commented] (KAFKA-12690) Remove deprecated Producer#sendOffsetsToTransaction

[ https://issues.apache.org/jira/browse/KAFKA-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363343#comment-17363343 ] A. Sophie Blee-Goldman commented on KAFKA-12690: Hey [~loboxu], as pointed out elsewhere

[jira] [Commented] (KAFKA-12843) KIP-740 follow up: clean up TaskMetadata

[ https://issues.apache.org/jira/browse/KAFKA-12843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363354#comment-17363354 ] A. Sophie Blee-Goldman commented on KAFKA-12843: This was pointed out on the PR, but

[jira] [Commented] (KAFKA-12689) Remove deprecated EOS configs

[ https://issues.apache.org/jira/browse/KAFKA-12689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363342#comment-17363342 ] A. Sophie Blee-Goldman commented on KAFKA-12689: Hey [~loboxu], this ticket is marked

[jira] [Commented] (KAFKA-12844) KIP-740 follow up: clean up TaskId

[ https://issues.apache.org/jira/browse/KAFKA-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363355#comment-17363355 ] A. Sophie Blee-Goldman commented on KAFKA-12844: As mentioned elsewhere, this ticket is

[jira] [Updated] (KAFKA-12898) Owned partitions in the subscription must be sorted

[ https://issues.apache.org/jira/browse/KAFKA-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12898: --- Fix Version/s: 3.0.0 > Owned partitions in the subscription must be sorted

[jira] [Commented] (KAFKA-8940) Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361196#comment-17361196 ] A. Sophie Blee-Goldman commented on KAFKA-8940: --- Hey [~mjsax] [~josep.prat] (and others),

[jira] [Commented] (KAFKA-12935) Flaky Test RestoreIntegrationTest.shouldRecycleStateFromStandbyTaskPromotedToActiveTaskAndNotRestore

[ https://issues.apache.org/jira/browse/KAFKA-12935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361367#comment-17361367 ] A. Sophie Blee-Goldman commented on KAFKA-12935: Hm, actually, I guess that could be

[jira] [Created] (KAFKA-12936) In-memory stores are always restored from scratch after dropping out of the group

A. Sophie Blee-Goldman created KAFKA-12936: -- Summary: In-memory stores are always restored from scratch after dropping out of the group Key: KAFKA-12936 URL:

[jira] [Commented] (KAFKA-12935) Flaky Test RestoreIntegrationTest.shouldRecycleStateFromStandbyTaskPromotedToActiveTaskAndNotRestore

[ https://issues.apache.org/jira/browse/KAFKA-12935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361374#comment-17361374 ] A. Sophie Blee-Goldman commented on KAFKA-12935: Filed 

[jira] [Commented] (KAFKA-12935) Flaky Test RestoreIntegrationTest.shouldRecycleStateFromStandbyTaskPromotedToActiveTaskAndNotRestore

[ https://issues.apache.org/jira/browse/KAFKA-12935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361359#comment-17361359 ] A. Sophie Blee-Goldman commented on KAFKA-12935: Hm, yeah I think I've seen this fail

[jira] [Commented] (KAFKA-12960) WindowStore and SessionStore do not enforce strict retention time

[ https://issues.apache.org/jira/browse/KAFKA-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367795#comment-17367795 ] A. Sophie Blee-Goldman commented on KAFKA-12960: +1 on pushing this responsibility to

[jira] [Assigned] (KAFKA-12984) Cooperative sticky assignor can get stuck with invalid SubscriptionState input metadata

[ https://issues.apache.org/jira/browse/KAFKA-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reassigned KAFKA-12984: -- Assignee: A. Sophie Blee-Goldman > Cooperative sticky assignor can

[jira] [Assigned] (KAFKA-12983) onJoinPrepare is not always invoked before joining the group

[ https://issues.apache.org/jira/browse/KAFKA-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reassigned KAFKA-12983: -- Assignee: A. Sophie Blee-Goldman > onJoinPrepare is not always

[jira] [Commented] (KAFKA-12896) Group rebalance loop caused by repeated group leader JoinGroups

[ https://issues.apache.org/jira/browse/KAFKA-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367805#comment-17367805 ] A. Sophie Blee-Goldman commented on KAFKA-12896: I believe this is caused by

[jira] [Created] (KAFKA-12983) onJoinPrepare is not always invoked before joining the group

A. Sophie Blee-Goldman created KAFKA-12983: -- Summary: onJoinPrepare is not always invoked before joining the group Key: KAFKA-12983 URL: https://issues.apache.org/jira/browse/KAFKA-12983

[jira] [Created] (KAFKA-12984) Cooperative sticky assignor can get stuck with invalid SubscriptionState input metadata

A. Sophie Blee-Goldman created KAFKA-12984: -- Summary: Cooperative sticky assignor can get stuck with invalid SubscriptionState input metadata Key: KAFKA-12984 URL:

[jira] [Commented] (KAFKA-12984) Cooperative sticky assignor can get stuck with invalid SubscriptionState input metadata

[ https://issues.apache.org/jira/browse/KAFKA-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17368542#comment-17368542 ] A. Sophie Blee-Goldman commented on KAFKA-12984: [~mjsax] Technically yes, the issue

[jira] [Updated] (KAFKA-12993) Formatting of Streams 'Memory Management' docs is messed up

[ https://issues.apache.org/jira/browse/KAFKA-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12993: --- Component/s: docs > Formatting of Streams 'Memory Management' docs is

[jira] [Created] (KAFKA-12993) Formatting of Streams 'Memory Management' docs is messed up

A. Sophie Blee-Goldman created KAFKA-12993: -- Summary: Formatting of Streams 'Memory Management' docs is messed up Key: KAFKA-12993 URL: https://issues.apache.org/jira/browse/KAFKA-12993

[jira] [Commented] (KAFKA-12920) Consumer's cooperative sticky assignor need to clear generation / assignment data upon `onPartitionsLost`

[ https://issues.apache.org/jira/browse/KAFKA-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360328#comment-17360328 ] A. Sophie Blee-Goldman commented on KAFKA-12920: While there does seem to be a possible

[jira] [Commented] (KAFKA-12925) prefixScan missing from intermediate interfaces

[ https://issues.apache.org/jira/browse/KAFKA-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360472#comment-17360472 ] A. Sophie Blee-Goldman commented on KAFKA-12925: [~sagarrao] do you think you'll be able

[jira] [Updated] (KAFKA-12925) prefixScan missing from intermediate interfaces

[ https://issues.apache.org/jira/browse/KAFKA-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12925: --- Fix Version/s: 2.8.1 3.0.0 > prefixScan missing from

[jira] [Commented] (KAFKA-12920) Consumer's cooperative sticky assignor need to clear generation / assignment data upon `onPartitionsLost`

[ https://issues.apache.org/jira/browse/KAFKA-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360480#comment-17360480 ] A. Sophie Blee-Goldman commented on KAFKA-12920: I believe we've found the real issue,

[jira] [Resolved] (KAFKA-12920) Consumer's cooperative sticky assignor need to clear generation / assignment data upon `onPartitionsLost`

[ https://issues.apache.org/jira/browse/KAFKA-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-12920. Resolution: Not A Bug > Consumer's cooperative sticky assignor need to

[jira] [Comment Edited] (KAFKA-12925) prefixScan missing from intermediate interfaces

[ https://issues.apache.org/jira/browse/KAFKA-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360472#comment-17360472 ] A. Sophie Blee-Goldman edited comment on KAFKA-12925 at 6/10/21, 12:51 AM:

[jira] [Commented] (KAFKA-12766) Consider Disabling WAL-related Options in RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342123#comment-17342123 ] A. Sophie Blee-Goldman commented on KAFKA-12766: Personally I agree that throwing an

[jira] [Updated] (KAFKA-12766) Consider Disabling WAL-related Options in RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12766: --- Fix Version/s: 3.0.0 > Consider Disabling WAL-related Options in RocksDB >

[jira] [Commented] (KAFKA-12749) Changelog topic config on suppressed KTable lost

[ https://issues.apache.org/jira/browse/KAFKA-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342120#comment-17342120 ] A. Sophie Blee-Goldman commented on KAFKA-12749: Thanks [~vishranganathan], assigned the

[jira] [Assigned] (KAFKA-12749) Changelog topic config on suppressed KTable lost

[ https://issues.apache.org/jira/browse/KAFKA-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reassigned KAFKA-12749: -- Assignee: Viswanathan Ranganathan > Changelog topic config on

[jira] [Commented] (KAFKA-12776) Producer sends messages out-of-order inspite of enabling idempotence

[ https://issues.apache.org/jira/browse/KAFKA-12776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344042#comment-17344042 ] A. Sophie Blee-Goldman commented on KAFKA-12776: Actually it turns out a KIP was just

[jira] [Updated] (KAFKA-12779) Use TaskId instead of String for the taskId field in TaskMetadata

[ https://issues.apache.org/jira/browse/KAFKA-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman updated KAFKA-12779: --- Description: Not sure why this was encoded as a String field instead of

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